Overview
Government and large enterprises can give partner organisations controlled access to shared services using Verifiable Credentials that prove role, scope, and authority.
Why it matters
Partner access is often negotiated manually and stitched into systems one by one. Credentials allow reusable, auditable access without bespoke integrations for every partner.
Ecosystem roles
- Issuer: The host agency or enterprise issuing partner authority credentials.
- Holder: Partner staff who need access.
- Verifier: The service or platform granting access.
Assurance and lifecycle
Access should be timeโbound and revocable. Verifiers must confirm issuer trust, scope, and status at each access request.
| Objective | Allow approved partners to access shared services. |
| Description | Issue role and scope credentials to partner staff and verify them at access time. |
| Actors | Host agency; Partner organisation; Partner staff |
| Dependencies | Trust registry and accreditation rules exist. |
| Preconditions | Partner organisation is accredited and staff are onboarded. |
| Postconditions | Access is granted within defined scope and time. |
flowchart LR
HOST@{icon: "fa:landmark", label: "Host agency", pos: "b"} -->|Issues partner VC| WAL@{icon: "fa:wallet", label: "Wallet", pos: "b"}
REG@{icon: "fa:book", label: "Trust registry", pos: "b"} -->|Publishes issuer trust| VER@{icon: "fa:id-badge", label: "Access service", pos: "b"}
WAL -->|Present VC| VER
VER -->|Grant scoped access| SYS@{icon: "fa:server", label: "Shared service", pos: "b"}
sequenceDiagram
participant Host as Host agency
participant Wallet
participant Partner as Partner staff
participant Verifier as Access service
participant Registry as Trust registry
Host-->>Wallet: Issue partner authority VC
Partner->>Verifier: Present VC
Verifier->>Registry: Validate issuer, scope, status
Registry-->>Verifier: Valid
Verifier-->>Partner: Access granted