Team and delegation¶
Your primary account manages access on the Team page of the customer portal; there is no API for it. Everyone you add signs in with their own user, an existing sub-account under your customer account. Addresses outside your organisation are refused.
Team members¶
A member has full access to ZERO-PROTECT: all services and branding. The Team page and the default posture for new services stay with the primary account. Removing a member takes effect within seconds.
Delegations¶
A delegation hands single services to another company, for example the end customer you run them for. Its members see and manage only those services. Add one under Team → Delegations:
| Field | Content |
|---|---|
| Name | who the services are delegated to, up to 64 characters |
| Services | any of your services, up to 500 |
| Members | email addresses of sub-accounts under your customer account, up to 100 |
| Members get | Members do not get |
|---|---|
| the delegated services with all settings, logs, charts, cache and certificates | your other services, also by direct link |
| health of these services and the edges that serve them | branding of the challenge and error pages |
| API keys that see only these services and follow the delegation, see API access | IP pools |
| the Team page, delegations and the default posture for new services |
- Once services are delegated, the service list shows a Tenant column: the name of the delegation, or your company name for services you keep.
- A full team member you add to a delegation keeps only the delegated services.
- Removing a delegation ends its members' access. The services stay yours, unchanged.