Organizations

Introduction

An Organization is the multi-tenant unit on the R9S platform — a shared workspace for a company or team. Organizations exist alongside personal accounts, and bring three things that personal accounts cannot:

• Shared billing — one credit balance and one billing entity for the whole team.
• Unified control — admins manage member quotas and permissions in one place.
• Programmable management — organization-scoped API keys let you pull usage and balance into your own finance and BI systems.

If you are an individual developer just trying out R9S, you don’t need an organization — keep using your personal account. Create an organization when you need to share a balance with a teammate, or when finance/ops want a single billing entity.

Account Model

R9S uses a Personal Account + Organization Account dual-stack model:

• Personal Account — The default account after login. Functions as a single-user workspace with its own credits and billing.
• Organization Account — A shared workspace for teams. Users can create or join multiple organizations.

Users switch between accounts using the Organization Switcher in the top navigation bar. The switcher allows seamless transitions between your personal account and any organizations you belong to.

Roles & Permissions

Each organization member is assigned one of three roles. Permissions are enforced both in the Portal UI and at the API level.

Role	Description	Key Capabilities
Owner	The organization creator or designated owner	All permissions, including transferring ownership and dissolving the organization
Admin	Trusted administrators	Member management, quota configuration, Management API Key creation, billing and top-up
Member	Regular team members	Use organization credits to make API calls, view personal usage statistics

Note

The platform currently supports these three fixed roles. Custom roles and fine-grained RBAC are not yet available.

Organization Lifecycle

Creating an Organization

1. Log in to the R9S Portal
2. Click the Organization Switcher in the top navigation bar
3. Select Create Organization
4. Enter your organization name in the dialog
5. Click Create — you will automatically become the Owner

Switching Between Accounts

Use the Organization Switcher to select:

• Personal Account — Return to your individual workspace
• Any Organization — Switch to that organization’s shared workspace

All actions (API calls, billing, usage) are scoped to your currently active account.

Inviting Members

1. Open the Organization Profile settings
2. Send email invitations to new members
3. Invitees receive an email with an acceptance link
4. Upon acceptance, they join as a Member by default

Leaving or Deleting an Organization

• Members / Admins can leave an organization through the Organization Profile settings
• Owners can dissolve the organization entirely (this action is irreversible)

Caution

Deleting an organization will permanently remove all associated data, including billing history and member records. This action cannot be undone.

Member & Quota Management

Accessible to Admin and Owner roles at Dashboard → Management → Members.

Member List

The member list displays:

Column	Description
Avatar & Name	Member’s profile picture and display name
Email	Account email address
Role	Role badge (Owner / Admin / Member)
Monthly Usage	Current month’s consumed credits with a progress bar against the quota limit

Use the search bar to filter by name or email. Results are paginated for large teams.

Per-Member Quota

Admins can set a monthly credit quota for each member to control spending:

Quota Value	Behavior
Positive number	Member can use up to this amount of credits per month
-1	Unlimited — no quota restriction
0	Disabled — member cannot make any API calls

To edit a member’s quota:

1. Find the member in the list
2. Click the Edit action
3. Enter the monthly quota value
4. Click Save

Default Quota

Navigate to Dashboard → Management → Settings to configure the default monthly quota for new members. When a new member joins the organization, this default quota is automatically applied.

Management API Key

Organizations have access to a dedicated Management API Key — a credential type that is physically separate from the standard API keys used for model calls.

See Management API Overview for an introduction to the available endpoints.

Feature	Standard API Key	Management API Key
Purpose	Call AI models (chat, embeddings, etc.)	Query account balance, usage, and billing
Prefix	sk_	sk_mg_
Scope	Model inference endpoints	Management API endpoints only
Who can create	Any member	Admin or Owner only

Management API Keys are bound to both the creating user and the organization, enabling full audit trails.

For details on creating and managing these keys, and for the available Management API endpoints, see Management API.

Billing & Credits

Organization billing is centralized — all members draw from a shared credit pool.

Credits Top-Up

• Navigate to the Credits page (visible to personal accounts and organization Admins/Owners)
• Purchase credits via Stripe
• Credits are added to the organization’s shared balance

Invoices & Billing History

• View billing details on the Billing page
• The invoice entity corresponds to the organization
• Each organization maintains a separate Stripe Customer record

Note

Only Admins and Owners can access billing pages and perform top-ups. Members can view their own usage but cannot manage organization finances.

Usage & Reporting

Usage Dashboard

The Portal provides usage dashboards at both individual and organization levels:

• Personal view — Your own token consumption across models and time periods
• Organization view — Aggregated usage for all members (Admin/Owner only)

Automated Reporting via Management API

For enterprise customers who need to integrate usage data with internal systems, the Management API provides programmatic access to:

Endpoint	Description
/balance	Query current organization credit balance
/usage	Retrieve token usage records within a specified time range

Common integration scenarios:

• Finance Systems — Automated daily billing data pulls for accounting
• BI Dashboards — Real-time usage monitoring and cost analysis
• Budget Alerts — Threshold-based notifications when credits run low

Typical User Journey

1. Register — A new user signs up and starts with a Personal Account
2. Create Organization — Use the Organization Switcher to create “Acme Inc.” and become the Owner
3. Invite Team — Send email invitations to colleagues; they join as Members
4. Configure Quotas — Admin sets monthly credit quotas for each member to prevent overspending
5. Set Defaults — Admin configures a default quota in Settings so new members are automatically capped
6. Enable Automation — Admin creates a Management API Key and provides it to the finance team for automated daily billing reports
7. Scale — As the team grows, new members inherit default quotas and start making API calls immediately

Key Design Principles

Principle	Description
Managed Identity	User and organization lifecycle is managed through a hosted identity provider, letting the platform focus on billing and quotas
Dual-Stack Accounts	Seamless switching between personal and organization accounts accommodates both individual developers and enterprise teams
Two-Level Quota Control	The organization holds the credit pool; quotas can be further allocated down to individual members
Credential Separation	Standard API keys and Management API keys are logical isolated, reducing the risk of privilege escalation
Programmable Management	The Management API enables organizations to consume their account data in automated workflows