How agencies and consultants can manage several client chatbots with scoped sub-admins, workspaces, backups, audit logs and branding controls.
If you run support chatbots for more than one business, you quickly hit an awkward question: who should be allowed to touch what? Giving every colleague full access to every client is risky. Making each person ask the account owner for every small change is slow. This article explains how to structure access with sub-admins, workspaces and roles so each person sees only the clients they look after, and how to keep changes recoverable.
The problem with "everyone is an admin"
Agencies, consultancies and in-house platform teams tend to start the same way. One person creates the agents, shares a login or invites a few teammates, and everything works until the client list grows.
Then the cracks show:
- A junior colleague edits the wrong client's agent because the dashboards look alike.
- A contractor finishes a project but still has access to every other client.
- Someone deletes a knowledge source and nobody can say who did it or when.
- A client asks, "Who has access to our chatbot?" and the honest answer is "probably more people than it should be."
None of this is a technology failure. It is an access-design failure. The fix is to separate who belongs to your team, who is responsible for which client, and what each person is allowed to do.
Three layers of access
It helps to think in three layers rather than one big permission list.
Layer 1: Workspaces separate the clients
A workspace is a container. A single account can hold several, and you switch between them from the header. The simplest rule for client work is one workspace per client (or per client brand). Agents, data sources and conversations then stay in their own space, and a mistake in one does not spill into another.
Agents can also be moved between workspaces. This is useful when you build a prototype in your own space and later hand it to the client's workspace.
Layer 2: Roles describe what a team member can do
Within a workspace, members hold a role. The built-in roles are Owner, Co-owner, Member, Support and Viewer, and individual members can have permission overrides on top of the role. That gives you room for cases such as "this person can edit knowledge sources but not change billing."
Two limits are worth knowing. Custom roles and SSO are Corporate-only and are hidden in the interface, and SSO/SAML sign-in is not something you can rely on today. Plan around the five built-in roles plus overrides.
Layer 3: Sub-admins are scoped to assigned clients
A sub-admin is different from a workspace member. A sub-admin is scoped to the clients assigned to them. Within that scope they can open the client dashboards and run backups or restores. Outside it, they have no reach.
This is the layer that suits an agency with account managers. Each manager looks after their own client list and cannot wander into anyone else's.
What a sub-admin can actually do
Be precise about this when you brief your team, because over-promising leads to confusion.
A sub-admin can:
- Open the dashboards of the clients assigned to them.
- Run backups.
- Run restores.
A sub-admin cannot reach clients that were not assigned to them, and they cannot delete a client's data on their own authority. That second point deserves its own section.
Deletion needs the client's approval
The most damaging mistakes are irreversible ones. For that reason, deleting through a sub-admin account requires a code that is emailed to the client. The client, not your agency, holds the final say on destructive actions.
This protects both sides. The client knows nothing disappears without their knowledge. Your team is protected from the situation where a rushed click wipes out months of tuning and the relationship takes the blame.
- 01Sub-admin requests deletion
- 02Code is emailed to the client
- 03Client shares the code
- 04Deletion proceeds
Make every change recoverable
Access control reduces mistakes. Recovery covers the ones that still happen. Several layers are available:
- Restore points: each agent can keep up to 40 restore points, so you can roll back to a known-good version of its persona and settings.
- Nightly backups: downloadable snapshots are created nightly, and the last 7 are kept.
- Trash: deleted agents sit in Trash for 30 days before they are gone.
- Duplicate: copying an agent duplicates its persona, model and training data, but not conversations. It is a safe way to experiment without touching the live version.
A practical habit: before any large change to a client's agent, such as rewriting the persona or replacing a set of sources, create a restore point and say in your change notes what you are about to do. If the result is worse, rolling back takes moments rather than an afternoon.
Know who changed what
When several people work on one client, accountability matters. The workspace Activity log, available to owners and admins under Workspace settings, records every create, edit, delete or upload with the name, email, feature and time. Each data source also shows who added it and who last edited it.
That turns awkward conversations into simple ones. If an answer suddenly changes tone, you can check whether a source was edited and by whom, rather than guessing.
Branding, domains and how the client sees it
Many agencies want the chatbot to look like part of the client's own site rather than a third-party tool. Three controls matter here:
- Remove branding: the Widget studio includes a remove-branding option. On the pricing page, "Remove Powered by AI SNS IO" is listed as an add-on at $99 per month.
- Custom domains: under Agent → Settings → Custom domains, you can verify a subdomain with a CNAME record, and it covers the embed script, the iframe and the agent link. This needs Hobby or higher.
- Welcome message: it is auto-translated into every language the widget speaks, which helps when a client serves customers on website chat, WhatsApp or Messenger in several markets.
Check the current price and plan on the pricing page before quoting a client, because an admin can change plan prices at runtime.
A sensible structure for a small agency
Here is one way to put the layers together. The numbers are a hypothetical illustration, not a recommendation for any particular size.
Imagine an agency with three account managers and twelve clients. Each client gets its own workspace. Each account manager is set up as a sub-admin scoped to four clients. The agency owner keeps the Owner role, and a client-side contact who only needs to read conversations gets a Viewer role in their own workspace.
The result:
- Each manager sees four clients, not twelve.
- A manager who leaves loses access to their four clients, and the other eight are unaffected.
- Clients keep the final say on deletion through the emailed code.
- The agency has restore points, nightly backups and the Activity log if anything goes wrong.
Remember the seat limits as well. Seats are 1 on Free, 2 on Hobby, 3 on Standard, 5 on Pro and 10 on Corporate, with Private AI unlimited. Count the people who need workspace roles before you pick a plan.
Doing this in AI SNS CHAT
Here is a practical walkthrough using the features described above.
- Create a workspace per client. Use the workspace switcher in the header to add one for each client, then create or move that client's agents into it. If you built a prototype elsewhere, use the agent move option to bring it across.
- Set team roles. Invite your colleagues and the client's contacts to the relevant workspace. Choose from Owner, Co-owner, Member, Support or Viewer, and add per-member overrides where a role is slightly too wide or too narrow. Check your plan's seat count first.
- Assign sub-admins to clients. Scope each account manager to the clients they are responsible for. They can then open those dashboards and run backups or restores, and nothing else outside their list.
- Brief the client on deletion. Explain that deletions made through a sub-admin need a code emailed to them.
- Set up recovery habits. Before major edits, create a restore point (up to 40 per agent). Know that nightly snapshots keep the last 7 and that Trash holds deleted agents for 30 days.
- Apply client branding. Open the Widget studio to use remove-branding (the "Remove Powered by AI SNS IO" add-on is $99 per month), and connect a client subdomain under Agent → Settings → Custom domains on Hobby or higher.
- Review activity. Owners and admins can open Workspace settings → Activity to see who created, edited, deleted or uploaded what and when.
To deploy on the channels your client actually uses, such as the website chat widget, WhatsApp or Messenger, see the Channels section of the dashboard and the connections overview. For the full capability list, visit features, and for security practices see security. Plan details are on the pricing page.
If you want a guide through the dashboard while you set this up, Synthia, the AI fleet manager, can walk you to the right screen and highlight the control, by voice or text.
For agencies that go further, Master Client workspaces unlock Prospector, which searches for businesses and builds one agent and one test link per company. It is a separate workflow from day-to-day client management, so treat it as an add-on to the structure above rather than part of it.
Frequently asked questions
What is the difference between a sub-admin and a workspace member?
A workspace member holds a role such as Member, Support or Viewer inside a workspace. A sub-admin is scoped to the clients assigned to them and can open those dashboards and run backups or restores. Use roles for people who work inside a client's space, and sub-admins for your own account managers.
Can a sub-admin delete a client's data?
Not on their own. Deleting through a sub-admin account needs a code that is emailed to the client, so the client confirms any destructive action. This keeps accidental or unauthorised deletions from going through.
Can I create custom roles for my team?
Custom roles are Corporate-only and hidden in the interface, so plan around the built-in roles (Owner, Co-owner, Member, Support, Viewer) and per-member permission overrides. SSO/SAML sign-in should not be assumed to be available either.
How do I hide the AI SNS CHAT branding on a client's chat widget?
The Widget studio includes a remove-branding option, and the pricing page lists "Remove Powered by AI SNS IO" as a $99 per month add-on. Check the pricing page for the current figure, since prices can be changed by an admin.
What if someone changes a client's agent badly?
Check the Activity log in Workspace settings to see who made the change and when. Then roll back using a restore point (up to 40 per agent) or a nightly backup (last 7 kept). Deleted agents also stay in Trash for 30 days.


