Agency Workspaces, Clients, and Roles
Manage many client domains with separate workspaces, roles, and branded reports.
Updated
An agency or managed service provider looks after domains that belong to other people, each of whom would prefer that the others not read their mail statistics. SpoofKiller’s answer is structural rather than a matter of filters: each client gets its own workspace, and access to a workspace comes from membership, never from knowing where to look. This page describes the structure, the five roles, and the tools built on top of it. The commercial overview is on the agencies page.
Agency organization and client workspaces
There are three kinds of organization. A standard organization is what every account starts with. Subscribing to the Agency plan turns it into an agency organization. An agency can then create client workspaces, each of which is a full organization in its own right, linked to the agency that manages it.
| Agency organization | Client workspace | |
|---|---|---|
| Holds | The agency’s own domains, its staff, the subscription, and report branding | One client’s domains, reports, sources, findings, alerts, sender rules, and API keys |
| Members | Agency staff | Optionally the client’s own people; agency staff reach it by inherited access |
| Plan and billing | The Agency subscription | None of its own. Every limit and feature comes from the agency’s plan |
To create a workspace, an Owner or Administrator of the agency opens Clients and enters the client’s name. To work in it, choose it from the organization menu; domains are then added to it exactly as in Getting Started, including ownership verification for each one.
Isolation
What the separation guarantees, stated as rules the software enforces on every request:
- Everything is scoped to one organization. A page, action, or API call operates on the active organization, and a domain is loaded only if it belongs to that organization. A valid domain id from another workspace returns “not found,” the same as an id that does not exist.
- Access comes from membership. A person can act in an organization only as a direct member or, for a client workspace, as a qualifying member of the agency that manages it. Knowing an id, a URL, or a domain name grants nothing.
- Client members see their workspace only. Someone invited to a client workspace cannot see the agency organization or any sibling client.
- API keys belong to one organization. A key created in a client workspace reads that workspace. No request can name a different organization; the organization is derived from the key.
- Reporting addresses and verification tokens are per domain, per workspace. Reports for a domain are attached to the workspace that verified it.
- Sender rules stay inside their workspace. An organization-wide rule in one client workspace has no effect on another, or on the agency.
One table is shared across all customers by design: a cache of public facts about IP addresses (reverse DNS, network, registry country). It holds no customer data. See Data Inventory, Retention, and Deletion.
The five roles
Each member has one role per organization. Roles are ranked, and each includes everything the roles below it may do. There are six permissions; the table shows the lowest role that holds each.
| Permission | What it covers | Client Viewer | Read-only User | Analyst | Administrator | Organization Owner |
|---|---|---|---|---|---|---|
| View | Dashboards, domains, sending sources, findings, alerts, DNS history, and reports on screen; own notification preferences | Yes | Yes | Yes | Yes | Yes |
| Export | Download reports as CSV or PDF | — | Yes | Yes | Yes | Yes |
| Classify | Classify senders and create sender rules; acknowledge, resolve, and reopen findings; upload report files; run a scan, blacklist check, or lookalike check on demand; review lookalikes; schedule reports | — | — | Yes | Yes | Yes |
| Manage domains | Add, bulk-import, verify, pause, and delete domains; set DKIM selectors, brand terms, and group labels | — | — | — | Yes | Yes |
| Manage members | Invite and remove members and change roles; create and revoke API keys; create client workspaces; edit organization name and report branding; set alert rules and pause alerts | — | — | — | Yes | Yes |
| Manage billing | Change the subscription, open the billing portal, and delete the organization | — | — | — | — | Yes |
In prose:
- Client Viewer may look. Dashboards and reports, nothing else. Intended for a client’s own staff.
- Read-only User may look and export.
- Analyst may also do the daily work: classify senders, handle findings, upload reports, run checks, and schedule reports.
- Administrator may also manage domains, people, API keys, client workspaces, branding, and alert settings.
- Organization Owner may also manage billing and delete the organization.
Three safeguards apply to role changes:
- Nobody can grant a role higher than their own, by invitation or by changing a role.
- Nobody can change or remove a member who outranks them.
- An organization always keeps at least one Owner; the last one cannot be demoted or removed.
Inherited agency access
Agency staff do not need to be invited to each client. A member of the agency organization whose role is Read-only User or higher automatically has access to every client workspace of that agency, with the same role they hold in the agency. An agency Analyst is an Analyst in every client workspace; an agency Administrator is an Administrator in each.
- A Client Viewer in the agency organization does not inherit access to clients.
- If a person is also a direct member of a client workspace, the higher of the two roles applies there.
- New client workspaces are covered immediately, and removing someone from the agency removes their inherited access everywhere at once.
- Inheritance runs one way. Membership of a client workspace gives no access to the agency.
- Deleting an organization requires a direct Owner of that organization. Inherited access, even at Owner rank, is not sufficient.
- Alert email for a client workspace goes to that workspace’s direct members. Agency staff with inherited access see the alerts in the app but are not emailed unless they are also invited to the workspace; see Alerts and Notifications.
Invitations
Owners and Administrators invite people from the Team page of whichever organization the person should join: the agency for staff, a client workspace for the client’s people. An invitation names an email address and a role.
- The invitation link is valid for 7 days and can be revoked before it is used. Only a hash of the link’s token is stored.
- Inviting the same address again replaces the earlier pending invitation.
- Members and pending invitations together count toward the plan’s member limit, which is 50 per organization on the Agency plan and applies to each workspace separately.
- An organization can send at most 30 invitations a day.
- Every invitation, role change, and removal is written to the organization’s audit log.
Bulk import
On the Agency plan, an Owner or Administrator can add many domains to the active workspace in one go by pasting a list, one domain per line (commas, semicolons, and spaces also separate entries).
- Up to 100 domains per batch. Larger lists are refused; split them.
- Repeated entries in the list are imported once.
- Each domain is validated, added, and given its first DNS scan, so every imported domain has a Protection Score straight away.
- The result lists the domains added and the ones skipped, with the reason for each: not a valid domain, already in the workspace, or the plan’s domain limit reached. Import stops at the first domain that would exceed the limit.
- Imported domains are unverified. Each still needs its own verification record before reports are accepted.
The import goes into whichever workspace is active, so switch to the client first. To triage a prospect list before adding anything, the domain health check runs the same scan without an account.
White-label report branding
The Agency plan includes white-label reports. Under organization settings, an Owner or Administrator can set a brand name and a contact line (and store a logo address, which must begin with https://). When a brand name is set:
- generated PDF reports carry the brand name on the cover in place of “SpoofKiller,” and the brand name and contact line in the footer of every page;
- the PDF’s creator metadata is the brand name;
- reports for a client workspace use the agency’s branding, so it is set once, in the agency organization.
Every report keeps its closing note, which says that figures come from DMARC aggregate reports sent by participating mailbox providers and are not a complete record of all mail, and that the Protection Score is a proprietary measure. That note is part of reporting honestly to your client and is not removable.
There are seven report types. Six describe one domain: Daily Security Summary, Weekly Domain Health Report, Monthly Executive Report, DMARC Authentication Report, Suspicious Sender Report, and DNS Change Report. The seventh, the Agency Portfolio Report, is run from the agency organization and lists every domain across the agency and its clients with client name, score, policy, pass rate, message volume, and status. Reports can be downloaded as CSV or PDF, scheduled daily, weekly, or monthly, and, on the Agency plan, scheduled to recipients outside the organization, such as a client who has no login.
Plan limits
| Limit on the Agency plan | Value | How it is counted |
|---|---|---|
| Domains | 50 | Shared across the agency organization and all of its client workspaces |
| Report files per month | 100,000 | Shared across the agency and its clients |
| Lookalike checks per month | 15,000 | Shared across the agency and its clients |
| Members | 50 | Per organization, including pending invitations |
| Reporting history | 730 days | Applies to every workspace |
| API requests per day | 20,000 | Per API key |
50 domains, one pool
The Agency plan is $49 a month, or $490 billed annually; the full comparison is on the pricing page. Client workspaces cannot start a subscription of their own.
Removing clients and the agency
Individual domains can be deleted from a workspace at any time by an Owner or Administrator, which removes the domain’s data and frees its place in the pool. Deleting the agency organization, which only a direct Owner of the agency can do, also schedules every one of its client workspaces for deletion. Access ends at once and the data is permanently removed within 30 days, as described in Data Inventory, Retention, and Deletion. To retire a single client while keeping the agency, delete that client’s domains, or ask us to remove the workspace.
