Agency plan
Clients organize reporting and allocation. Protected sites do the actual verification.
In an Agency workspace, a client represents the customer, brand, or account you manage. A protected site represents a production domain or property that receives its own site key, backend secret, domain rules, usage history, and security settings.
Client names are unique inside one organization after whitespace and case normalization. Different organizations can still use the same client names for their own customers.
A reporting and allocation container for one customer or account.
The actual integration unit with keys, domains, widget code, and verification settings.
A valid holding state for sites you create now and assign later.
Recommended workflow
Create one client for each customer or managed brand.
Optionally reserve part of the monthly protected attempt pool per client.
Create one protected site per production domain and attach it to a client when known.
Use the clients page to compare site health, domains, and protected attempt usage.
Unassigned sites
A protected site does not need a client when it is created. Choose No client when you want to provision keys first, test a property before assigning ownership, or migrate existing sites into the agency structure gradually. You can assign or reassign the client later from the protected site configuration tab.
Attempt allocation
Monthly attempt allocation lets you reserve part of the organization pool for a client. When a client reaches its allocation, new widget challenges for that client’s protected sites are blocked while unassigned sites and other clients can continue if organization usage remains available.
| Blank allocation | The client can use the shared organization pool without a client-specific cap. |
|---|---|
| Client allocation | The client has a monthly cap inside the organization limit. |
| Unallocated pool | The remaining organization attempts that can be assigned to new or existing clients. |
Client cleanup
Deleting a client never deletes protected sites silently. If a client has no sites, it can be deleted directly after confirmation. If sites are still attached, choose Delete and unassign sites to move those sites to No client, or reassign the sites first.