Can a client have read-only access to their own workspace?
Yes. Roles grant one of five permission levels per module, and mailbox access can be read-only, so a client can watch without editing.
Marketing, communications, and growth agencies
One workspace per client. One login for the agency.
For the agency owner adding a seat and a login for every new client, the fourth client stops being the breaking point. Each account gets its own sealed workspace, the team gets one login, and a lead approves what a junior drafts.
CommsOperator gives an agency one workspace per client, each with its own connected Microsoft 365 mailboxes, contacts, pipelines, campaigns, and client-branded widgets, while the agency keeps one login and assigns account teams by role. Roles carry one of five permission levels per module, so juniors draft and leads approve. AI drafts wait in an approval queue, and every approval is on record for the client to see.
Monday morning
What usually goes wrong
- Client number four means another shared-inbox subscription and another set of logins to manage.
- Juniors need to draft and leads need to approve, and our tools have no idea which is which.
- Clients want a branded help center and feedback widget on their site, and we are quoting custom development.
- Monthly reporting means exporting five tools into one deck.
How it works
What changes for the team
- 1
A client workspace in one sitting
The client's IT approves the Microsoft 365 connection once, contacts come in by import, pipelines are set, and account team members are assigned by role.
- 2
Juniors draft, leads approve
Roles carry one of five permission levels per module. AI drafts wait for review, and a policy pack can require a second approver on sensitive accounts.
- 3
Client-branded widgets without custom development
Help center, chat, feedback, roadmap, and changelog, branded per client with their colours and welcome text, embedded on the client's site with one script tag.
- 4
Campaigns leave from the client's own domain
Sequences send from the client's own Microsoft 365 mailboxes and newsletters go through the client's chosen delivery provider, each with the client's own opt-out list, so the client's reputation and consent records stay theirs.
What you end up with
- Client data sealed per workspace, with explicit membership per account team
- An approval trail you can show a client
- Branded widgets on the client's site without custom development
- One login and one instance across every account
Who this is for
The agency owner adding a seat and a login for every new client, and the account lead who needs juniors to draft and leads to approve
Marketing, communications, and growth agencies
Proof from the portfolio
Tech Family Ventures brands running this today
Tech Family Ventures product studio
Nine product workspaces on one instance. Each launch gets early-access capture, a booking link, a private roadmap, and agent-readable feedback on day one.
Chief in Tech
An executive network's newsletter, event follow-ups, and site widgets, in a workspace sealed off from the fund that shares its name.
Frequently asked questions
Can widgets be fully white-labelled?
Widgets are branded per workspace: colours, position, and welcome text. A fully unbranded application shell is not offered; the widgets are what carry the client's brand.
Can we hand a client their data if they leave?
Yes. Exports are provided on request today; self-serve bulk export is on the roadmap.
Start with the part that hurts
Access is by request. Tell us what breaks first in your week and a person will say whether CommsOperator fixes it today or not yet.