Tenant-scoped identities
User names and external identifiers remain unique inside the owning tenant.
A security-first identity source for people and groups.
Create tenant-bound users and groups, enforce versioned lifecycle changes, remove inactive identities from group authority, and preserve audit evidence.
- Tenant-scoped identities
- Versioned changes
- Terminal deprovisioning
What you can evaluate
Lifecycle controls that fail closed.
Versioned changes
Stale lifecycle updates are rejected instead of overwriting newer state.
Terminal deprovisioning
A deprovisioned identity cannot silently return to active status.
Group authority removal
Suspension and deprovisioning automatically remove group membership.
Follow 2AYE Directory from identity to evidence.
Each consequential action moves through the same six control points. See where 2AYE evaluates authority, requests human review, and preserves the outcome.
- 01IdentityWho or what is acting
- 02IntentSigned purpose and limits
- 03PolicyDeterministic evaluation
- 04ApprovalA named human when required
- 05ExecutionSingle-use grant, redeemed at the resource
- 06EvidenceReceipt joined to the audit chain
A practical adoption path
Start with one consequential workflow. Prove the boundary before expanding.
Assess
Document the environment, threat model, and integration boundary.
Design
Select protocols, signals, policies, and failure behavior.
Validate
Test vendor-specific APIs, tenant isolation, and abuse paths.
Release
Mark available only after deployed end-to-end verification.
What this includes
- Tenant-scoped users and groups with unique external identifiers
- Versioned lifecycle changes that reject stale updates
- Terminal deprovisioning
- Group authority removed on suspension and deprovisioning