Permissions are inherited org-wide. Per-skill granular overrides take priority.
Built-in Role Permissions Matrix
Default capability rights for organization members
| Permission | Owner | Admin | Member | Viewer |
|---|---|---|---|---|
| Manage billing | — | — | — | |
| Manage team | — | — | ||
| Delete skills | — | — | ||
| Publish skills | — | |||
| Create API keys | — | |||
| View analytics | ||||
| View skills |
Custom Roles
ENTERPRISETailored access tiers for specialized corporate functions
Release ManagerCUSTOM
Can publish and deprecate skills; no team or billing management permissions.
2 members assigned
Analytics ReaderCUSTOM
Read-only access to all ingestion graphs and CSV exports across packages.
1 members assigned
Security AuditorCUSTOM
Full visibility into immutable audit logs, IP geolocations, and API key prefixes.
1 members assigned
Publish Approval Workflow
Require multi-admin sign-off before releasing packages to the public registry
0 publish requests currently pending approval
Auto-Approve Patch Versions
Allow semver patch releases (0.0.x) without approval
Per-Skill Explicit Overrides
Granular package-level overrides that beat org roles
| Skill | Assignee | Permission | Action |
|---|---|---|---|
| @acme-labs/security-scanner | Elena Rostova (Viewer) | Can View Code & Run | |
| @acme-labs/code-analysis | David Kim (Member) | Admin / Maintainer |