Skip to content

Roles and Permissions

Decibyl has two independent role systems. Organization roles describe your standing inside one account and are what almost every customer cares about. Staff roles are a Decibyl-internal tier for people who support accounts they don’t belong to.

They are separate on purpose: being an Owner of your own organization gives you no reach into anyone else’s, and a Decibyl support engineer needs cross-account reach without being a member of every account.

Organization roles

Every membership carries exactly one role. They are ordered, and permission checks ask “is this member at least this role” — so an Owner passes any check an Admin would.

RoleRankWhat it means
member0Full use of the product — build workflows, run campaigns, place calls, read usage.
admin1A reserved middle tier. See the note below.
owner2Everything a member can do, plus managing who else is in the organization.

What Owner-only actually covers

Today, exactly one area is Owner-gated: membership management.

  • GET /organizations/members — list members and their roles (any member may call this)
  • PATCH /organizations/members/{user_id} — promote or demote — Owner only
  • DELETE /organizations/members/{user_id} — remove a member — Owner only

Everything else in the product — workflows, agents, campaigns, telephony, API keys, usage — is available to any member of the organization.

The last Owner is protected

An organization can never be left with zero Owners. Both demotion and removal refuse if the target is the only Owner remaining:

{ "detail": "Cannot demote the last owner. Promote someone else first." }

This is a deliberate dead-end guard. An account with no Owner would have nobody able to manage membership, and no way to recover through the API.

To hand over an account: promote the new Owner first, then demote or remove yourself.

Staff roles

Staff roles are set by Decibyl, not by customers, and are independent of organization membership. A user with no staff role — which is almost everyone — is simply not staff.

RoleRankReach
support0KYC document review across accounts. Read-and-review, no further reach.
superadmin1Everything support can do, plus the billing dashboard, platform provider credentials, and superuser operations.

The split exists because the staff surfaces are not equivalent in risk. Reviewing a KYC document is cross-account but bounded. Changing billing rates, reading platform provider keys, or acting as another account can move money or expose secrets — so those need the higher tier.

Because the tiers are ranked, superadmin passes every support check without needing a separate grant.

What happened to your existing team on upgrade

If you had an account before roles existed, nothing about your access changed.

  • Every existing member became an owner. Before this feature, all members of an organization had identical, unrestricted access. Backfilling anyone to a lower role would have silently taken away something they could do the day before, so everyone was placed at the top tier.
  • Every existing superuser became a superadmin — the top staff tier, matching the single all-or-nothing flag they had before.

New members joining after the upgrade default to member. An Owner promotes from there.

Checking your own role

The authenticated-user response includes your role in your currently selected organization, so the UI can show or hide member-management controls without a second request.