The five roles
You pick a role when you invite someone, and you can change it later.
The split is between running the shop and setting it up:
- A manager runs it day to day — products, stock, invoices, and how the storefront looks.
- An admin does all of that and sets the store up: its name, its web address, which coins it takes, and the API keys and webhooks.
- A developer only runs the integration — API keys, webhooks, and replaying failed webhook deliveries.
- A member can look at everything and change nothing.
- Only an owner can move where the money goes or change who is on the team.
Why some things are admin-only
Two of these look like ordinary storefront settings, and are not. Your web address and your custom domain. A manager can restyle the whole shop but cannot rename it. Changing your address breaks every checkout link already out there — in emails, in chats, in invoices your customers have not paid yet. Which coins you accept. Every role can see your payout addresses, but only an owner can set one. Switching on a coin whose network has no payout address is a mistake a manager cannot fix, so it sits with an admin.Invite someone
Press Invite Member, enter their email address, and choose Admin, Manager, Developer or Member. There is no owner option — see Handing a store over. They need a Taberna account on that email address already. If they do not have one, ask them to sign up first, then invite them.
The team list, with one pending invitation.
A developer cannot edit products in the dashboard. If a developer needs to create
products or top up stock from your own software, they can mint an API key with the
products:write scope — managing keys is exactly what the role is for.Change someone’s role
Use the dropdown on their row. It takes effect immediately and does not ask you to confirm, so aim carefully. Two things you cannot do:- Change your own role. Your row shows a plain label instead of a dropdown.
- Demote the last owner. Every store keeps at least one.