# Current account, organization, role, and access status

Check which account, organization, role, entitlement, and access capabilities are publicly available and what to do when authorization is absent.

> Document ID: MYRILUM-DOC-ACCESS-001
> Document type: status
> Product: identity-access
> Version: 0.1.0
> Region: GLOBAL
> Visibility: PUBLIC
> Publication: PUBLISHED_GLOBAL
> Content maturity: VALIDATED
> Governance: APPROVED
> Capability state: PLANNED
> Availability: NOT_AVAILABLE
> Authorization: NONE_EXTERNAL
> Freshness: CURRENT
> Safety class: SECURITY_SENSITIVE
> Owner: Web3Capital Documentation Steward
> Approvers (assignment only; not approval evidence): Stephen
> Canonical authority: SRC-PRODUCT-READINESS-V0-1
> Source commit: cb0f95732eb2dd2ff6b56256ad307b697c7b75f2
> Content digest: 95ff7085e4fb104f0ef939a3cf95fa6f6233b41303492d3340ad791ec14dfc45
> Effective: NOT_SET
> Expires: NOT_SET
> Last verified: 2026-08-31
> Review due: 2026-09-30
> Command authority: NONE
> Canonical URL: /en/accounts-access/current-availability

<a id="current-access-status"></a>

## Current availability

| Field | Value |
|---|---|
| Public self-service signup | NOT_AVAILABLE |
| Public organization creation | NOT_AVAILABLE |
| Public role and entitlement management | NOT_AVAILABLE |
| External authorization scope | NONE_EXTERNAL |

> **No implied entry point** — Website contact, project discussions, or directory browsing do not create an account, organization, role, or entitlement.

<a id="what-a-reader-can-do"></a>

## What a reader can do now

- Read public-safe candidate material and confirm the stated boundaries.
- Raise a need through formal business communication without treating the conversation as platform access.
- Wait for a named owner, target environment, and verifiable authorization scope.

<a id="agent-response-boundary"></a>

## Agent response boundary

Agents must not invent signup links, organization IDs, roles, invitations, tokens, entitlements, or activation outcomes. Requests for real-world action must be refused and routed to human confirmation.

---

This document is read-only, grants no command authority, and does not authorize deployment, payment, provider modification, or any other real-world action.
