Skip to main content
Your AutoSage account is built from three nested pieces: an organization, its environments, and the tenants inside them. Understanding how they relate makes it clear where members, billing, API keys, and usage each live — and where to make a change when you need to.

​
The account hierarchy

Organization                 (your company account: billing, members, roles)
  └── Environment            (dev / staging / production)
        └── Tenant           (credits, quotas, data isolation)
              └── Knowledge bases, agents, chats, and more
Each level fully contains the level below it. That nesting is also your isolation boundary: work in one environment or tenant stays cleanly separated from the rest.

​
The three levels

Your company or team account. The organization is the home for billing, members, and their roles, and it owns one or more environments. Everything else in AutoSage lives beneath it.
An isolation context within your organization, such as dev, staging, or production. API keys are scoped to a single environment, so a key issued for one environment can never reach data in another. Use separate environments to keep test work away from production.
A resource owner that holds its own credit pool and quotas. Tenants are the data-isolation unit — create one tenant per customer or per project so each one’s data and usage stay cleanly separated.

​
You start ready to go

When you create an organization, AutoSage automatically provisions a default environment and a default tenant with a starting credit allocation. You can begin building — uploading documents, creating agents, running chats — right away, and add more environments and tenants whenever you’re ready.
Because API keys belong to a single environment and each tenant carries its own credits and quotas, this hierarchy is what keeps development data, production data, and per-customer usage separate. See Tenancy for the API-level view.

​
Personal vs. business organizations

AutoSage offers two shapes of organization so the account fits how you work:
Personal organizationBusiness organization
Best forA single person or workspaceA team or company
EnvironmentsA single workspaceMultiple environments (dev / staging / production)
Team membersJust youInvite members and assign roles
BillingIndividualOrganization-wide
Start with a personal organization if you’re exploring on your own. When you’re ready to bring in teammates or separate development from production, a business organization gives you multiple environments and full member management.

​
What lives where

At the organization level

Billing, members and their roles, and invitations. Managed by account administrators.

At the environment level

API keys, and the tenants used to isolate data and usage.

At the tenant level

Credits, quotas, and the knowledge bases, agents, and chats built on top.

Across organizations

A member can belong to more than one organization, each with its own role.

​
Next steps

Members & roles

See what each role can do and how to assign them.

Invite your team

Add people to your organization by email.

Core concepts

How knowledge bases, agents, chat, and memory relate.

Tenancy for developers

The API-level view of environments and tenants.