Skip to main content

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:
The creator is automatically assigned the 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

Managing members

Invite a member

Admins can invite members by email:
The role field defaults to member if omitted.

List members

List your organizations

Returns all organizations you belong to, including your role in each.

Org policies

Admins can set enforced preferences that override member personal settings: Enforced policies cannot be overridden by individual members or per-request parameters. They take the highest precedence in the context pack assembly hierarchy.

Shared memories

Memories scoped to org 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”)
Org memories are injected into every request made by any member, alongside their personal and workspace-level memories.

Organization credits

Each org has its own credit pool with subscription_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.

Admin dashboard

The org admin dashboard provides a summary view and audit trail:

Deleting an organization

Only admins can delete an organization:
Deleting an organization removes all members, shared memories, and credit balances. This action cannot be undone.