Agencies
An agency account manages client organisations. Each client is a separate organisation with its own sites, consent logs, incidents and people, so one customer's data never mixes with another's. The agency's team can work in all of them.
Access
Everyone in the agency organisation can open every client, with the role they hold in the agency: an agency editor is an editor in each client, and an agency viewer is a viewer. Invite the client's own people from the client's Organisation page; they see only that client.
| Role | Can |
|---|---|
| Viewer | See sites, banners, scans, incidents and consent statistics |
| Editor | Also edit and publish banners, manage domains, run scans, roll out templates |
| Admin | Also manage members and API keys, look up and export consent records, create clients |
| Owner | Also manage billing |
Clients
The Clients page lists each client with its sites, unpublished banners, open incidents and consents over the last 30 days. Create a client there, then switch to it from the organisation menu. Incident emails for a client go to its own admins and to the agency's.
Templates across clients
Create a banner template in the agency organisation and roll it out to sites in any client. Each site keeps its own privacy policy link, and each publish must pass that site's checks. The rollout reports which sites were published, which were already up to date, and which failed and why.
Branding
Under Clients → Branding, set your name, logo and accent colour. Your clients' users then see your brand instead of PXL Consent in the dashboard, on invitation pages, and in invitation and incident emails, which are sent with your name as the sender. Your own team keeps the normal look.
Plan and billing
Clients use the agency's plan. Limits such as the number of sites count the agency and all its clients together, and the agency receives a single bill. If the agency's payment fails, publishing pauses in its clients too; live banners keep working and consent is still recorded.