Platform
Organizations
Create teams, manage members, and publish org-scoped artifacts on agex.
Overview
Organizations let teams collaborate on artifacts under a shared namespace. Instead of publishing as @rkrebs/team-rules, you publish as @acme-corp/team-rules — owned by the organization, editable by members.
Creating an organization
- Go to Settings → Organizations or
/app/orgs - Click New Organization
- Choose a name and slug (the slug becomes your org namespace:
@slug/...) - Add a description (optional)
The slug must be unique across both usernames and organization names.
Roles
| Role | Permissions |
|---|---|
| Owner | Full control — manage members, change roles, delete org, manage billing |
| Admin | Add/remove members, edit org artifacts, manage settings |
| Member | View private artifacts, create and edit org artifacts |
Org-scoped artifacts
Artifacts can belong to an organization:
- Published under the org namespace:
@acme-corp/nextjs-rules - Editable by any org member (based on role)
- Can be private (visible only to org members)
- Version reviews and maintainers work within the org context
To publish under an org, select the organization in the "Publishing as" dropdown when creating or editing an artifact.
CLI usage
Org artifacts work the same way in the CLI:
agex add @acme-corp/team-rules
agex run @acme-corp/deploy-skill
agex sync # syncs all artifacts including org-owned onesPlans
Organization plans unlock team features:
| Feature | Free | Team ($6/user/mo) | Enterprise ($18/user/mo) |
|---|---|---|---|
| Public artifacts | ∞ | ∞ | ∞ |
| Private artifacts | — | ∞ | ∞ |
| Members | 5 | Unlimited | Unlimited |
| RBAC | — | ✓ | ✓ |
| Audit log | — | ✓ | ✓ |
| Analytics | — | ✓ | ✓ |
| SSO (SAML/OIDC) | — | — | ✓ |
| Self-hosted option | — | — | ✓ |
Manage your plan at Settings → Billing or contact sales at hello@agex.dev.