How tenancy works
- Sign up creates a tenant. You provide an Organization Name (which becomes a URL slug), your name, email, and password. The first user is the tenant Admin.
- Sign in is two-step. Enter your tenant name, then your credentials. If you belong to more than one tenant, use Switch tenant to pick another.
- Data is scoped by tenant. Every connection, project, and key belongs to exactly one tenant.
Sign-in uses ORCA’s own email/password accounts, independent of Oracle. There is no SSO today.
Roles
Each user has one role per tenant. There are two:| Role | Can do |
|---|---|
| Admin | Manage users, connections, the API key, and agent settings — plus everything an Analyst can do. |
| Analyst | Use the app: run conversions, chat, and view connections and users. Cannot manage users or admin-only settings. |
Platform admins are a special case — an Admin whose tenant is the BTSS platform tenant. They manage tenants (see below). It’s a derived capability, not a third role.
Manage users
Admins add and manage users in Settings → User Management.Add a user
Click Add User, then enter an Email, a Password, an optional Display Name, and a Role (Analyst or Admin).
Platform admins: managing tenants
BTSS platform admins get a Tenants tab (only visible from the platform tenant). From Settings → Tenants they can Create Tenant (Name + Slug), see all tenants with user counts, and expand a tenant to add or remove its users. This is how new customer tenancies are provisioned.Regular tenant admins never see this tab — it’s BTSS-internal provisioning.
Next steps
The AI engine
Add the Anthropic key that powers the ORCA agent.