Mandates
Run compliance for several client organizations from one place, see which client needs you first, and show each client your brand instead of devguard's.
A mandate is the account of a consultancy, a vCISO practice or an MSP (managed service provider) that runs compliance for its clients. Each client is its own organization under the mandate, with its own register (its controls, policies, risks and evidence), its own people and its own audit log. Your team gets one list of all clients, one queue of their open tasks and one portfolio report.
What a mandate gives you as a partner:
- Your clients see your logo in the app, not devguard's.
- devguard bills you, not your clients. Your clients never get an invoice or a payment reminder from devguard.
- If a payment of yours fails, your clients keep working until 14 days after the paid period ends.

You set up once:
- Get a mandate
- Buy licenses
- Put your brand on it
- Add a client
- Copy one client's setup into another
- Give your team access to clients
Then, in the daily work:
- See which client needs attention
- Work through the open tasks
- Send the portfolio report
- Detach a client
Scripts and integrations: see For developers below.
Get a mandate
You cannot switch on a mandate in the app. devguard support turns one of your organizations into a mandate. To ask for it, book a consultation. The offer starts at five licenses.
Buy licenses
Each client uses one license, and a demo client uses none; it still works on the mandate's Business plan. You pay for every license you hold, whether a client uses it or not.
- In the sidebar, open Billing.
- Choose Monthly or Yearly and complete the payment.
- Under How many licences, set the number with the minus and plus buttons, then choose Save.

More licenses take effect at once and are prorated. A lower number takes effect at the end of the billing period, never below the licenses in use. From the moment you schedule it, you can add clients only up to the lower number. To add more, choose Keep the current licences, which cancels the reduction.
Put your brand on it
Do this before the first client, so the client sees your brand from the first day.
- Open Branding. Upload your Full logo and set the Primary color and Secondary color.
- Open Settings. Under Support, enter a Support email and a Help URL, then choose Save.

Your Company links replace devguard's legal links in your clients' footer. Without them, the footer keeps devguard's site notice, privacy policy and terms. The report uses your mandate's name, logo and colors. Support in your clients' user menu opens your Help URL. If you leave it empty, it opens devguard support.
Add a client
- Open Clients and choose Add client.
- For a new client, choose New organization in the Add client menu. Enter the Name and choose Create.
- For an organization that exists already, choose Attach existing organization, choose it and then Attach. It keeps all its data.

Each client uses one license, a demo client none. You can attach only an organization that you own, that is under no other mandate, and that pays for no subscription of its own.
A new organization has no people of its own. Invite the client's staff to it, so they can take it over if you ever detach it.
Copy one client's setup into another
- Open Templates.
- Under Client to copy from, choose a client and then Download template. You get a JSON file.
- Under Client to copy into, choose the new client. Choose Choose file and select the file.
- Check the preview, then choose Copy into and confirm.

The copy brings:
- frameworks and their coverage links
- policies, as drafts
- risks, treatment actions, assets and vendors
- evidence requirements, record categories and record templates
- processes, trainings, tasks and questionnaires
- business roles, without their members
- definitions, acronyms, labels, locations, variables, schedules and the asset, threat and vulnerability classes
It leaves behind members, files, images, comments, reviews, assessments and all history. It also leaves out a questionnaire condition that cannot be read or names an id the questionnaire does not have, since it has no effect.
Watch out: you cannot remove copied entries from this page. Existing entries, archived ones too, are never overwritten.
How your team reaches the clients
Your colleagues work in each client with the role they have in the mandate. You do not invite them into each client.
| Role in the mandate | Clients they reach | Role in the client |
|---|---|---|
| Owner, admin | Every client | Same role |
| Member, auditor | Only the clients switched on under Access | Same role |
| Employee, external | None | None |
A change in the mandate (invite, role change, deactivation, removal) applies in every client the person reaches. The client cannot remove your team or change their roles.
For people who had a role in a client before it joined, see Earlier roles in a client.
Give your team access to clients
- Open People and invite the person to the mandate as Member or Auditor.
- Open the person and go to the Access tab.
- Under Client Access, switch on each client they work for.

Switch a client off to take access away. The person leaves the client at once. Their tokens and app connections for that client stop working. This does not apply if they had their own role there before. Only owners and admins of the mandate change access.
See which client needs attention
- Open Clients. Clients with overdue tasks come first and show Needs attention.
- Read Coverage, Overdue and Due soon (the next 30 days) for each client.
- Click a client's name to open its dashboard.

The figures are kept for five minutes. After a change in a client, choose Refresh.
Work through the open tasks
- Open Work queue. It lists the open tasks of all clients, grouped by client, with the most urgent client first.
- Start at the top. Overdue dates are red. Tasks without a deadline come last.
- Click a task. devguard switches to that client and opens the task.

The queue shows the 50 most urgent tasks across all clients. Some clients have no tasks in those 50, or no open tasks at all. Their group is collapsed, and its header still shows the counts.
Send the portfolio report
- Open Report and choose Generate Report.
- If you want, enter a Custom Footer and choose Save. It is not kept for the next report.
- Choose Download PDF.

The report has an executive summary, one row per client (coverage, open work, next audit, last activity), the clients with overdue work and the upcoming audits.
Detach a client
Detaching ends your team's access and frees the license. The organization keeps its data and moves to the free plan.
- Open Clients. In the client's row, open the menu and choose Detach from this mandate.
- Turn on Hand it to the client if the client continues with devguard on its own. The client's own admins and members then get an email with a link. If the organization has no owner left, one of them can become its owner and pay devguard directly.
- Choose Detach.

The client's own owners, admins and members get an email either way.
The detach is refused if nobody of the client's own would be left to open the organization, or, with Hand it to the client on, to take it over (an auditor cannot). Invite someone into the client and have them accept the invitation first, or export its data. If you attached your own organization, you are removed from it.
Reference
Who can open the mandate pages
Owners, admins, members and auditors of the mandate. A person in no mandate is sent to their dashboard, and a deactivated person cannot open the pages. Opening a mandate page makes the mandate your active organization, and the sidebar shows the Mandates section.
Earlier roles in a client
A person may already have a role in a client before it joins the mandate:
| Earlier role in the client | While they are in the mandate | When the mandate role ends |
|---|---|---|
| Member, auditor, employee or external | The higher of the two roles | The earlier role comes back |
| Owner or admin, and owner or admin in the mandate | The mandate role | Removed from the client |
| Owner or admin, and member or auditor in the mandate | Their own role | Their own role |
Permissions
| Action | Owner, admin | Member, auditor |
|---|---|---|
| Clients, Work queue, Report | Yes (all clients) | Yes (their clients) |
| Read the mandate's Audit Log | Yes | Yes |
| Add, attach, detach clients | Yes | No |
| Templates, Branding, Billing, Settings | Yes | No (hidden, changes refused) |
| Change client access | Yes | No (can see own) |
Billing
- One license per client; a demo client uses none.
- Clients work on the mandate's Business plan.
- After a failed payment, clients keep the plan until 14 days after the paid period ends. After a cancellation there is no grace. Then the clients fall back to the free plan.
Limits
- A client cannot be a mandate itself.
- A mandate that still has clients cannot be deleted.
- A template carries at most 5,000 entries per section. An import counts against the receiving client's plan limits. When the plan has too little room, the preview names each section over its limit, with what the template adds and what the plan still allows, and the copy is refused until the client's plan has room.
Audit log
The mandate's Audit Log lists added and detached clients, access changes and license changes. Access changes and template copies also appear in the client's audit log.
For developers
Mandates have no public API. The mandate pages use internal endpoints with the user's session; they are not in the API reference.
- A connected app (OAuth grant) or an API token scoped to one organization cannot read the Clients list or the Work queue.
- An API token that is not scoped reaches every client its owner reaches, in the same role.
- To work inside a client, call the normal API with the client's
organizationId. It is in the client's Settings under Organization UUID.
F='{"nextReviewAt":{"type":"date","preset":"overdue"}}'
curl -sS -G "https://app.devguard.ch/api/evidence/" \
-H "Authorization: Bearer $DG_TOKEN" \
--data-urlencode "organizationId=$CLIENT_ORG" \
--data-urlencode "filters=$F"DG_TOKEN is an unscoped API token of a person who reaches the client. CLIENT_ORG is the client's Organization UUID.
How is this guide?