Working With Clients
Build and operate automations across separate client workspaces from a single login. Each client gets their own isolated workspace governed by delegation grants. Workflows, connected accounts and run histories stay completely separate.
Choose the path that fits your practice
Select your role during onboarding to configure your console and client consent screens:
Consultant
Projects delivered to clients, then handed over.
MSP
Client automations you run and maintain on an ongoing basis.
Both paths share the same core features: delegation grants, recorded session access, cross-workspace pushes, and a unified management console.
What does differ is the shape of the work, and it shows up in three places in this section:
| Consultant | MSP | |
|---|---|---|
| Bringing a client in | Inviting them to create the workspace makes the handover cleaner: it is theirs from day one. | Creating it yourself suits a workspace you will be operating. |
| Grant duration | Set it to the length of the engagement, and leave management when you are done. | The default two years fits an ongoing relationship. |
| When it ends | You leave; the client keeps every workflow you built. | It does not, usually. Reviews and scope changes take the place of an ending. |
For MSPs & IT Service Providers
Managed Service Provider (MSP) Practice
MSPs govern ongoing IT operations across dozens or hundreds of client tenants with strict SLA commitments and recurring revenue models:
- Your Stack: PSA service boards (HaloPSA, ConnectWise, Autotask), RMM agents (NinjaOne, Datto RMM), Directory services (Microsoft 365, Entra ID, Google Workspace), EDR threat feeds (SentinelOne, Huntress, CrowdStrike), and CSP billing (Pax8).
- Core Problems Solved: Eliminating technician toil on high-volume Tier-1 tickets, automating JML user provisioning and session revocation, catching unbilled SaaS license leakage, and enforcing compliance audits.
- Operational Workflow: Build reusable patterns in your primary workspace, review each one-client preflight before pushing, then monitor execution activity from your MSP Dashboard.
- Key Resources:
Nothing above is enforced. They are the defaults that tend to fit, and each is covered where it comes up.
Already signed up as an Individual / Team? The answer is not fixed — tell your account team which path fits and they will move you across.
Getting set up
Start on your own, and the last step is a short conversation with us. Everything except the client layer is yours from the moment you sign up: your workspace, your workflows, your connected accounts.
Sign up and say what you are
Signing up names your workspace, then asks who you are on the Choose your role screen: Individual / Team, Consultant or MSP. Choose the one that describes your practice. The answer is recorded against your account and is what we work from, so it is worth answering accurately rather than picking the middle option. See Account & Authentication.
Build in your own workspace
Start by connecting your own accounts and building workflows in your workspace. Once the client layer is enabled, the push process copies a reviewed workflow into each client’s workspace.
We turn the client layer on with you
Multi-tenancy changes how billing, access and client consent work across your account, so we switch it on together rather than leaving it behind a toggle. Tell us roughly how many clients you manage and what you want to automate for them, through Support or your account team, and the console appears on your workspace. From there the rest of this section applies.
Onboarding support, architecture reviews and the billing arrangement for your practice come with it. Billing works per client workspace today, so bring how you invoice your own clients and we will fit it to that.
The rest of this section
The pages below follow the order the work actually happens in.
The model in one place: what each client’s workspace holds, what a grant permits, and what crosses between them. Written so you can hand it to a client who asks.
1. How Multi-Tenancy WorksThree ways to bring a client in: create their workspace, invite them to create it, or request access to one they already have.
2. Client OnboardingConfirm what your access permits, how it is scoped, and how a client narrows or ends it before you work in their workspace.
3. Governance & ImpersonationFollow one client from approved access through deployment, testing, Live operation, monitoring, and handover.
4. Your First Client WorkflowCompare a reviewed one-client Admin Push with a rollout from a selected saved version before following either procedure.
5. Choose a Deployment MethodEvery client in one view: execution health, cross-client activity, and where something is failing.
6. Your ConsoleProtocol matrix and architecture across PSA, IAM, RMM, Security, and Billing with OAuth and REST steps.
7. Supported IntegrationsSearchable catalogue of commonly used MSP platforms, with connection methods and setup links.
8. App DirectoryExample patterns for onboarding, offboarding, security triage, billing reconciliation, endpoint maintenance, and lifecycle reporting.
9. Automation BlueprintsWhat’s Next?
👉 How Multi-Tenancy Works → — the model in one page, opening with a two-minute walkthrough. Then Client Onboarding, which is where the work starts.