An organization shares policies, exceptions, investigations, webhooks and API receipts among its members. The server decides every permission; the table below is the same permission table the app uses to explain a refusal.
Roles
| Role | Edit policy drafts | Simulate a draft against past verdicts | Submit a draft for activation | Activate a submitted policy (not their own) | Request an exception on a verdict | Decide an exception (not their own) | Manage members | Read the audit log |
|---|---|---|---|---|---|---|---|---|
| owner | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| admin | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| compliance | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | — | ✓ |
| risk | ✓ | ✓ | ✓ | — | ✓ | — | — | ✓ |
| analyst | ✓ | ✓ | ✓ | — | ✓ | — | — | — |
| viewer | — | — | — | — | — | — | — | — |
| api | — | — | — | — | — | — | — | — |
Oversight
- A policy submitted by one member must be activated by another; the server refuses self-activation.
- Policy exceptions are requested by one member and decided by another, and every decision is written to an append-only audit log.
- Investigations are opened, prioritised and closed by people. The AI assistant can be asked about a case but cannot create, change or close one.
- Every call to an AI model is recorded with digests and sizes, so what was sent and when can be shown without keeping a second copy of the text.
Integrations
Organization API keys record receipts as the organization's (API). Governance events are delivered to your endpoints with a signature (Webhooks).
Plans and contract terms are on the Enterprise and pricing pages. NOSHASHI holds no security certification (such as SOC 2 or ISO 27001) and makes no claim of regulatory compliance. It is software that reads the ledger and applies rules; the decisions stay yours.
Generated from src/lib/org/governance.ts · src/lib/org/webhooks.ts · src/lib/trust/boundary.json