Documentation Index
Fetch the complete documentation index at: https://docs.a21e.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Organizations let teams share credits, enforce policies, and manage access. Every member inherits org-level settings while keeping their own personal workspace and preferences.Creating an organization
Create an org from the dashboard at Settings > Organization > Create, or via the API:admin role. A slug is generated from the name for URL-friendly references.
Organization creation via API is restricted to web app sessions — API keys cannot create organizations.
Roles
| Role | Permissions |
|---|---|
| Admin | Full access: manage members, set policies, view audit log, delete org |
| Member | Use org credit pool, inherit org preferences and memories |
Managing members
Invite a member
Admins can invite members by email:role field defaults to member if omitted.
List members
List your organizations
Org policies
Admins can set enforced preferences that override member personal settings:| Policy | Effect |
|---|---|
model_tier: economy | Prevents members from using standard/premium models |
risk_tolerance: low | Forces conservative outputs for all members |
auto_execute: false | Requires manual review before execution |
Shared memories
Memories scoped toorg are visible to all organization members. Use them for:
- Team coding conventions (“We use kebab-case for URL paths”)
- Architecture decisions (“Our API uses Fastify, not Express”)
- Project context (“The billing service is in
apps/billing”)
Organization credits
Each org has its own credit pool withsubscription_balance and addon_balance, separate from member personal balances. When a member’s personal credits are exhausted, org credits are used (if allowed by policy).
See Credits & Billing for details.