{"slug":"platform/identity-authority-view","title":"12 · Identity & Authority View","section":"platform","sectionLabel":"Platform","status":"unclassified","type":"document","path":"platform/identity-authority-view.mdx","bytes":3032,"description":"IW One Auth — organizational identity, user identity, AI identity, agent identity, roles, authority, tenancy, permissions, approvals, and delegation.","updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n## Identity Answers Who Is Acting\n\nEvery action in SpineWorkspace is **identity-bound**. No anonymous Work, no ambient capability access.\n\n```text\nIW One Auth\n   ├── Organizational identity (tenant)\n   ├── User identity (human)\n   ├── Twin identity (twin:{userId})\n   ├── Agent identity (agent:{agentId})\n   └── Roles → Authority → Permissions → Approvals → Delegation\n```\n\n\n**Tenancy is the isolation boundary.** Business Context Spine, projections, capabilities, and memory are all tenant-scoped. Cross-tenant access is a governance decision, not a default.\n\n\n## Identity Types\n\n| Identity | Example | Scoped to | Memory it carries |\n|---|---|---|---|\n| **Organization / Tenant** | `tenant:{orgId}` | Organization | Organizational Memory (THE memory) |\n| **User** | `user:{userId}` | Tenant + roles | Personal Contextual Memory (serves BC) |\n| **Twin** | `twin:{userId}` | Same tenant as its human | AI Continuity Memory (serves BC) |\n| **Spine Agent** | `agent:{agentId}` | Tenant + Work + role | Agent Continuity (serves BC) |\n\nTwin identity derives from its human. Agent identity derives from the Work and the organizational role it represents.\n\n## Authority vs Permission vs Approval\n\n* **Authority** — what this identity may do in this Business Context (derived from role + policy + Work context).\n* **Permission** — the enforceable gate that checks authority at capability resolution time.\n* **Approval** — a human or delegated authorization that satisfies a governance policy for a specific plan.\n* **Delegation** — scoped, auditable grant of authority (e.g., \"approve renewals under $X in this Work\").\n\n```text\nIdentity → Authority (who/what may act)\n   → Capability (what can be done)\n     → Policy (under what constraints)\n       → Approval (who said yes, with what evidence)\n         → Authorization (governance verdict → Hermes may execute)\n```\n\n## Tenancy & Isolation\n\n* One Spine per tenant. One projection per participant per Work.\n* No capability or memory leaks across tenants. The operational sandbox is per-tenant and per-Work-context.\n* Delegation never crosses tenant boundary without explicit governed action.\n\n## Where to Go Next\n\n<CardGroup cols={2}>\n  \n    Policy → plan → approval → authorization — the verdict Hermes obeys.\n  \n  \n    How each identity connects to ecosystems via One Auth scopes.\n  \n  \n    Secrets, audit, provenance, isolation, fail-closed behavior.\n  \n</CardGroup>\n"}