Run MarqIQ for several clients
One workspace holds one client. That is not a recommendation you can work around: a workspace is the boundary for the reporting, the connected tools, the seats, the bill and the data store, and an account belongs to exactly one of them. This page sets out the shape that works, what it costs you in sign-ins, and what to tell a client before you point an audit at their CRM.
Before you start
There is no workspace switcher
Your account belongs to one workspace and there is no control that moves it to another. Eight clients means eight sign-ins, each under a different email address. Plan for that before you start, because it shapes how you hand work to a colleague later.
Note
Inviting an address that is already registered to another workspace is refused with "This email is already registered to a different workspace". Use a separate address per client. An alias on your own domain is enough: an invited address is not put through the sign-up checks that a new workspace goes through.
Plan required
Every workspace carries its own plan, its own seat count and its own payment. Nothing is pooled. Business is the tier most agency work lands on — ten seats and four connected tools in any mix, so a client running two CRMs through a migration still fits.
Why one workspace per client, and not one with everything in it
Every figure MarqIQ produces is measured across one workspace. Put two clients in one and their contacts, deals, form fills and sources are counted together, and no filter unpicks them afterwards.
- The connected-tool allowance is per workspace. Two clients in one workspace spend one allowance on two CRMs, which Starter and Pro refuse outright because they allow one tool per category.
- The tracking script is issued per workspace, so two clients in one workspace share a script and a set of first-party cookies.
- The synced records from a workspace's tools sit in a database created for that workspace, rather than in a table everyone shares.
- Access is per workspace. A client you give read access to would otherwise be reading another client's numbers.
Set up a client
The cleanest arrangement is the one where the client owns the workspace and invites you into it. The subscription sits with them, the connected-tool credentials are theirs, and the relationship survives you handing the account to a colleague.
Ask the client to sign up with a work address on their own domain.
Sign-up refuses a personal or throwaway address, asks for a real company name, and checks that the email domain receives mail. A free trial starts at 14 days with the Pro feature set, 5 seats and 2 connected tools. They then confirm their email from a link before they can sign in. The link works once and expires in 24 hours.
Ask them to invite you from Team & roles with the Agency Collaborator role.
That role connects and configures tools, and withholds the three things a client should not hand over: billing, the member list, and disconnecting a live tool. It cannot write to their records, fields, forms, workflows or templates either. It can upload an image for a template draft, and that image is stored in their HubSpot or Marketo.
Accept the invitation at the link, using an address you have not used on another MarqIQ workspace.
The link lasts seven days and works once. You set your own name and password on the join screen; the address is fixed by the invitation.
Connect the client's tools from Integrations.
Copy the Workspace ID from Account settings into whatever you use to keep track of clients.
It is a six-digit number, unique across MarqIQ, and it is what support asks for. It saves you describing a client by name in a case.
Tip
Where a client will not or cannot own the subscription, sign the workspace up yourself under an address at your own domain and name the organisation after the client. You then hold the billing and the credentials, and moving the workspace to the client later is a conversation with support rather than a button.
Moving between clients
Click Sign out at the foot of the sidebar.
Sign in with the address that belongs to the other client's workspace.
Note
A signed-in session lasts seven days, so a separate browser profile per client keeps several open at once without signing in again each time.
What is shared across your workspaces, and what is not
| Thing | Shared? |
|---|---|
| Your sign-in | No. One account, one workspace, one address. |
| Plan, seats and payment | No. Each workspace is bought and renewed on its own. |
| Connected tools and their credentials | No. Each workspace holds its own, encrypted. |
| Synced records, reports and dashboards | No. Each workspace has its own store. |
| Saved UTM naming conventions and URL rules | No. They belong to the workspace that made them. |
| Support cases | No, and not even within a workspace. A case belongs to the person who raised it. |
| AI assistant access tokens | No. A token reads the one workspace it was made for. |
Note
A Partner arrangement exists for agencies and resellers and is not sold self-serve. Its limits are agreed rather than published, and checkout refuses a workspace on it with "This workspace is billed under an agreement — talk to us to change its seat count." Raise a case from Support if you want that conversation.
Give a client their own numbers without giving them your setup
Open Team & roles in the client's workspace.
You need the Workspace Admin role to invite anyone. An Agency Collaborator cannot, so ask the client's admin to do this or hold the admin role yourself.
Click Invite Member.
Type the client contact's email address.
Choose Executive Viewer from the role list.
It reads the dashboards and reports, changes nothing at all, and cannot pay for a plan or for seats.
Click Send invite.
Take care
Each seated client contact holds one of that workspace's seats. Starter seats three people, Pro five and Business ten, and a pending invitation holds a seat as firmly as a member does.
Before you run an audit on a client's CRM
Tell them these four things first. Each is true of every connected tool, and each is the kind of thing a client would rather hear from you than discover.
- MarqIQ reads their records and stores a copy. Analyses run on that copy, not on a live query per click.
- MarqIQ writes to their records only when somebody in the workspace starts it. A change set is the reviewed way: a before-and-after list of every record, approved and applied by a workspace admin, filling empty fields only. The first-touch fill and writing standardised or enriched values back have no approval step and cannot be undone, so agree with the client who holds Manage before either is run.
- The credentials they give you are the ceiling. A token granted read-only scopes cannot write, whatever anyone asks MarqIQ to do.
- What MarqIQ builds inside their tool is theirs and stays if they leave — the properties, the hidden fields on their forms, the first-touch workflow and every value written onto a record.
Tip
The Integration Audit Report is on every plan and reads without changing anything, so it is the right first thing to run on a new client. Run it before you propose work, not after.
If it did not work
"This email is already registered to a different workspace"
Why: An account belongs to exactly one workspace, and the address you used is already in another one.
Fix: Invite a different address. An alias on your own domain works, because an invited address is not put through the sign-up checks.
A client workspace shows a second CRM cannot be connected
Why: Starter connects one tool and Pro two with one per category, so a second CRM is refused even where an allowance is left.
Fix: Move that workspace to Business, which connects four tools in any mix and names two CRMs as allowed. The limit belongs to that workspace alone.
You cannot invite anyone into a client workspace
Why: Inviting is checked against the Workspace Admin role on the server. Agency Collaborator does not hold it, and the Invite Member button is not drawn for it.
Fix: Ask the client's admin to send the invitation, or ask them to make you an admin of their workspace.
A colleague cannot pick up a support case you raised
Why: Cases are held against the person who raised them, not the workspace. Your colleague's case list shows only their own.
Fix: Forward the case number, and ask them to raise their own case referencing it. Include the six-digit Workspace ID so support can tie the two together.
One client's term has ended and their tracking has gone quiet
Why: When a term ends the workspace becomes read-only and capture stops with it, so new form submissions are refused rather than stored for later.
Fix: Renew that workspace. The gap starts the day the term ended, so check the dates on every client workspace you run rather than only the one that was reported to you.
You want one bill for eight clients
Why: There is no self-serve arrangement that spans workspaces. Each one is bought and renewed on its own.
Fix: Raise a case from Support and ask about a Partner arrangement, whose terms are agreed rather than published.
Next steps
Related articles
Was this article helpful?