Why Billing is missing

What it is

Billing and Developer are the two settings tabs only the account owner can see. They are not hidden behind a permission you could be granted — there is no billing permission in the product at all, and no role or API key can be given one.

If either tab is missing from your Settings, exactly one of two things is true:

1. You are a member of this workspace rather than its owner, or
2. You own a workspace, but you are currently switched into somebody else's.

The second is far more common than people expect, and it looks identical to the first.

When you would use it

When a teammate says "there is no Billing on my screen". When your own Billing vanished after you joined a client's workspace. Or when you are deciding who on your team needs to be able to pay for things.

Where to find it

Dashboard → Settings. Billing and Developer appear there if — and only if — you are the owner of the workspace you are currently in.

To check which workspace that is, open the account switcher in the user menu, or go to Dashboard → Accounts.

Steps

1. Open the account switcher. If it says Acting in {some other name}, you are in someone else's workspace.
2. Switch back to My account — see Switch accounts.
3. Wait for the reload, then open Settings. Billing and Developer should be back.
4. If they are still missing and you are certain you own this workspace, confirm you are signed in with the right login. A second account created at some point in the past is a different workspace with a different owner.
5. If you are genuinely a member rather than the owner, ask that workspace's owner. There is nothing they can grant you short of making the purchase themselves.

Why it works this way

Three reasons, all of which hold up under pressure:

A workspace has one owner, and that owner pays. Letting a member change the plan means somebody who is not the account holder can increase what the account holder is charged. Every role in Agentency stops short of that boundary.

Consultants and agencies work in client workspaces. If Billing followed your role, an Admin at an agency could see and change a client's subscription. Keeping it with the owner means switching into a client's workspace can never expose their card details, their invoices, or their spend.

API keys are the same surface. A key acts as its owner, so if keys could be minted by a member, a member could quietly acquire ongoing access to the owner's account. Keys stay owner-only for exactly the same reason billing does — see Create a personal access token.

What a member can still do

Almost everything else. Depending on their role, a member can build and edit chatbots, load knowledge, read and manage conversations, work the customer list, configure Call actions, connect channels, manage the website widget, and — with the right role — manage other members.

What they cannot do:

• See the plan, the price, the invoices, or the payment method.
• Upgrade, downgrade, cancel, or buy an add-on.
• Buy message credits, even when the workspace has run out and chats have stopped.
• Create, see, or revoke API keys.
• Delete the account.

A member who hits a limit gets a clear message naming it. They just cannot resolve it themselves — see Roles and permissions.

Practical arrangements that work

Finance needs invoices. Either the owner downloads them, or the owner login is what finance uses. There is no read-only billing role. See Payment method and invoices.

The owner is on holiday and credits run out. Nobody else can top up. Buy a credit pack in advance if this is a real risk — packs never expire, so an unused buffer costs nothing. See Buy more credits.

An agency manages a client's account. The client stays the owner and pays; the agency joins as an Admin and does the work. Nobody has to share a password, and the client keeps control of their own subscription.

The owner is leaving the company. This is the hard case, because ownership is not a self-serve setting. Deal with it before they go rather than after — contact support and describe the situation.

Limits and plan notes

There is no billing permission to grant. Not to Admin, not through a custom permission set, not with any API key.

A member can still see the effects of billing. Limit messages name the plan, and a member who tries to create a chatbot over the cap is told the cap is the reason. They just cannot see the numbers or change them.

Developer follows exactly the same rule. Wherever this article says Billing, it applies to API keys too.

The tabs hide, they do not error. Nothing looks broken; the entries are simply absent. That is why "I think my account is broken" is such a common first report.

Common problems

I am an Admin and still cannot pay.

Expected. Admin means "runs the workspace", not "pays for the workspace". Only the owner can.

I own my workspace and Billing is gone.

You are switched into another one. Open the switcher and return to My account.

Can the owner give me Billing just this once?

No. The product will not attach billing to a role. If a purchase has to happen, the owner makes it — or, if this is a recurring problem, the workspace has the wrong owner.

Should I create a second account so I have my own Billing?

No. A second sign-up is a separate workspace with a separate plan and no access to the chatbots you actually work on. It solves nothing and doubles your bill — see What is an account?.

Our chatbot stopped and the owner is unreachable.

Nothing in the product will help. Plan ahead: buy a credit pack as a buffer, or make sure a second person has the owner login through your own password-management process.