Skip to main content
This guide is for agencies and consultancies running GEO monitoring for more than one client brand in Qwairy. It connects the pieces you’ll actually reach for: how to isolate each client’s account, how much access to give them, how to make the experience look like yours, and how to report back to them. Before onboarding your first client, make three decisions:
  1. Isolation model: does each client get their own contained account, or do you manage every brand under one team?
  2. Access model: does the client just view reports, or do they actively manage their own brand?
  3. Branding: does the client see Qwairy, or does the experience look like your agency’s own product?
The rest of this guide walks through each decision and the setup that follows from it.

Choose an access model

The core decision is how much a client sees and controls. Qwairy gives you two mechanisms, and they serve different situations: Use a Virtual Team when the client needs to manage the brand rather than only read it. Viewer access stays read-only and brand-scoped within your organization, while a sub-team transfer gives management access in a separate team context. If neither fits: for example, you’re a small team managing a handful of client brands yourself, with no client logins at all: you can simply keep everything under one team and control brand access per team member instead.
Virtual Teams is available on Business, Enterprise, and Agency Business plans, or through an explicit feature override.

Set up a client

To give a client a fully isolated, self-service account for their brand:
1

Create a sub-team for the client

Go to Team Management > Virtual Teams and click Create. Name it after the client, and allocate a credit amount and workspace quota from your organization’s pool.
2

Move or create the client's workspace in it

Either tick the workspace under Move existing workspaces while creating the sub-team, or move it afterwards with Move workspace. The workspace’s full monitoring history travels with it: nothing resets.
3

Invite the client's team members

Switch to the client’s sub-team and go to Team Management > Members to invite them. Their client access is limited to workspaces inside that sub-team.
Only Owners and Managers of your parent organization can move workspaces, and they retain access to every sub-team automatically without a separate invitation.
If you’d rather keep the client’s brand inside your own organization and just let a stakeholder check the numbers, skip the sub-team and add them as a Viewer scoped to that one brand instead.

Apply agency branding

Once a client is set up, you can make the whole experience look like your agency’s own product instead of Qwairy’s:

Custom Logo

Replace the Qwairy logo across the dashboard, shared reports, and login.

Custom Domain

Serve the dashboard and login from your own subdomain, e.g. analytics.yourcompany.com.

Remove Branding

Hide the platform attribution on shared pages and reports.
White-labeling is an Enterprise capability, configured under Team Management > White Label. See Agencies overview for the full picture, including fully white-labeled authentication via SSO.

Report to clients

Several ways to get results in front of clients, depending on whether they have a Qwairy login:
  • Pitch Audits: create pre-sales audits for prospects before onboarding them into a full workspace, with prompt review, AI answer evidence, detected competitors, cited sources, and shareable reports.
  • Shared links: generate a public URL for a dashboard, brand perception snapshot, GEO Matrix, competitor comparison, or prompt signals view. No Qwairy account needed on the client’s end, and links can be set to expire or revoked at any time.
  • Weekly report emails: enable the per-workspace weekly report so clients get a recurring summary without checking the dashboard.
  • Outbound webhooks: if your agency has its own reporting systems, route Qwairy’s notification events to your own endpoint as signed JSON instead of Qwairy emails. This is an Enterprise capability; configure it under Team Management > White Label and see Developers > Webhooks for the payload format.