Team and permissions
Invite teammates, assign roles, and control exactly what each person can do.
Add people to your store and decide what they can access under Settings → Team.
Invite a team member
- Click Invite Member.
- Enter their Email Address and choose a Role (below).
- (Optional) Restrict them to specific sales channels, or fine-tune individual permissions in the Permissions panel.
- Click Send Invitation and they'll get an email with a link to join.

Roles
| Role | What they can do |
|---|---|
| Owner | Everything, including billing and team management. This is the store creator. |
| Manager | Full store access including apps: they can browse the app store, install, configure and uninstall apps, your payment provider included. They can also view your API keys (not create or revoke them). Out of reach: billing, webhooks and the developer portal. Can manage team members. |
| Staff | Edit existing products, work orders, and adjust inventory. Can't create products, cancel orders, issue refunds, delete products, or manage the team. |
| Viewer | Read-only access to products, orders, and analytics. |
Need something in between? Adjust any member's permissions individually, and they'll show a Custom badge.
Who can change the plan or the card
Only the account owner. Billing is the one area that is not governed by the permission checkboxes at all. It is tied to the account that owns the store.
Managers, Staff and Viewers do not see Settings → Billing. The entry is not in their settings menu, and it is not hidden by a permission you can grant. It is absent because the plan, the card and the invoice history all belong to the account that owns the store, not to the store. Nothing is broken and nothing is missing from their account; there is simply no billing for them to reach.
There is a Manage billing checkbox in the Permissions panel. Ticking it does nothing at all: no page appears and no billing action becomes available. Treat it as inert. If a teammate needs to pay the bill, transfer ownership of the store to them, because there is no way to delegate billing without it.
Manager can uninstall your payment provider. That is the most expensive thing this role can do, and it is on by default. If you do not want it, open the member's Edit Role & Permissions and untick Install & Uninstall Apps, and they keep everything else.
Manage members and invitations
- Open a member's ⋯ menu to Edit Role & Permissions or Remove Member.
- Under Pending Invitations, you can Resend or Revoke an invite that hasn't been accepted yet.
Removing a member, or editing their role, also cuts off any AI tool they had connected to this store. That happens automatically and it cannot be reversed by putting the role back. Read Removing someone also disconnects their ChatGPT or Claude connection before you edit a member who has one, because it is a one-way door.
Removing a member does not delete API keys they created. Keys belong to the store, not to the person who made them, so a key that person set up keeps working after they are gone. If you are removing someone for cause, go to Settings → Authentication → API Keys afterwards and delete or rotate anything they set up. See Connect an AI assistant.
Removing someone also disconnects their ChatGPT or Claude connection
If a team member connected ChatGPT, Claude, Cursor or another AI tool to this store by signing in with their Brainerce account (see Connect an AI assistant), removing them from the team also cuts that connection off. Their AI tool still shows Brainerce in its own list, but every action it tries against your store is refused from then on.
Editing their role or their permission checkboxes cuts it off as well, in either direction. Promoting a Staff member to Manager disconnects their AI tool exactly as demoting them would. The connection was approved against the permissions that person held on the day they set it up, and Brainerce will not quietly hand it a different set of permissions afterwards, so it stops the connection instead.
Opening the member form and saving it unchanged does nothing. The check compares what you saved against what was already stored, so a save that moves neither the role nor the checkboxes leaves a working connection alone. Only a real change disconnects.
Putting the role back does not bring the connection back. This is the part that surprises people. Demote someone by accident, notice, and promote them straight back, and their AI tool is still cut off. There is no button anywhere in your dashboard that reconnects it. The person themselves has to go into their AI tool, remove the Brainerce connection, add it again and approve the permissions again. Until they do that, their AI tool reports that it cannot reach your store.
It affects this store only. If that person is also on the team of another store of yours and has connected an AI tool there, that connection is untouched.
Timing. In normal operation the connection stops working straight away. If the disconnect itself fails behind the scenes (a hiccup on our side), their AI tool keeps working until it next renews its access, which is at most an hour. If you are removing someone for cause and that hour matters, change any API keys and passwords they knew as well, rather than relying on this alone.
This does not touch API keys. A brainerce_... key that person created keeps working after they are removed, because keys belong to the store. Delete or rotate those yourself under Settings → Authentication → API Keys.
What each role can ask the AI assistant to do
BOBO, the AI assistant in your dashboard, now checks a person's role before it makes a change. For most changes, if a person cannot make it by clicking through the menus, asking BOBO to make it for them is refused too, with a short message telling them to ask someone with the right permission.
Three things follow from that, and they catch people out:
- Viewers cannot use BOBO at all. The Viewer role does not include Use AI Assistant, so the assistant is closed to them rather than merely limited.
- Staff can ask BOBO for everyday work only. Editing products, updating stock, moving orders along and fulfilling them all still work. Gift cards, loyalty, pricing formulas, donations, blog posts, pages, standing orders and email campaigns do not: those need a Manager or the Owner, in the dashboard and through BOBO alike.
- Gift cards and donations are Owner-only unless you grant them. They are not in the Manager role's default set, so a Manager asking BOBO to issue a gift card is refused. That is not new, and it matches what the dashboard already did; tick the gift-card permissions on that member if you want them to have it.
The refusal happens before the approval card appears, so a person without the permission never sees a plan to approve. They see the refusal instead.
To close the assistant to someone completely, untick Use AI Assistant on their member record, or move them to Viewer. Without that permission there is nothing for them to ask it. If you are removing someone for cause, do that as well as the role change.
How many people you can add
Team size depends on your plan:
| Plan | Team members |
|---|---|
| Free | 1 (just you) |
| Pro | 3 |
| Growth | 5 |
| Enterprise | Unlimited |
See Plans & limits for the full comparison, or upgrade your plan to add more seats.
Transferring ownership of a store
Further down the Team page is Store ownership transfer, which hands the whole store to someone else's account. It is not the same as making somebody a Manager: the new owner gets the store, and you do not keep it.
Transferring a store on a paid plan goes through checkout, because the plan has to be attached to the receiving account's billing. The recipient accepts through a link they are sent.
Take a backup before you start, and be sure you mean it: this moves the store out of your account.
Payments are paused after a store transfer
The moment the new owner accepts, the store stops taking payments. Customers can still browse, add to cart and reach checkout, but the payment step fails with a "payments are temporarily unavailable" error until the new owner connects a payment provider. This is deliberate: the old owner's Stripe account is disconnected from the store's payment app at that moment, and the store must not charge a single order into the wrong bank account while it changes hands.
The pause ends only when the new owner connects a payment provider and its connection test passes. Any payment gateway app counts: Stripe, Cardcom, Grow, Morning or another. With Stripe, the pause lifts once Stripe reports that the account can take charges, which can be a few minutes after the connect click. Do it under Apps → Browse → Payment Gateways, following Configure payment methods.
Three things that do not end the pause, because people expect them to:
- Waiting. There is no timer. A store that was transferred three weeks ago and never had a provider connected is still refusing payments today.
- Installing the app without connecting it. A payment gateway that shows as Pending on the Installed tab has not passed its connection test, so payments stay paused. It has to show as Active.
- The old owner's other providers. Only the Stripe connection is removed by the transfer. A Cardcom, Grow or Morning connection set up by the previous owner stays in place, but it is still the previous owner's account receiving the money. Reconnect it with your own credentials, or disconnect it and connect a provider of your own.
A successful test order does not prove payments are back. Sandbox test orders on a test sales channel are not paused, so a test checkout completes normally while every real customer is still turned away. Check that the provider shows as Active instead.
If customers are still getting the payment error after the provider shows as Active, email [email protected] with the store name and say the store was transferred.
What's next?
Need help with your team? Email [email protected].