Manage client accounts

Create and maintain agency client workspaces with clear ownership, project boundaries and plan allowances.

Agencies and account owners

Feature availability

Product, package, provider and deployment boundaries for this page.

Available from
Current documentation
Deployment modes
cloud

Product screenshots

Current customer-safe screenshots are generated from the application so examples do not drift from the product.

Generated customer-safe screenshot of the WebRiskOps agency client account controls.

Before you create a client workspace

Client accounts keep agency work separated by client while allowing the agency to manage projects, reports and allowances. Use this page when an agency account needs a dedicated workspace for one client before scans, reports or white-label sharing begin. Create one client account per client organization. Do not combine unrelated clients in the same workspace just because the same agency user manages them.

Create a client account

Follow the path `Agency → Agency workspaces → Create client account → Client accounts → Client project`.

  1. Open /agency and find the agency workspace that owns the client relationship. Result: the Agency workspaces panel shows plan state, scan allowance, client limits and existing client projects.
  2. In the Create client account form, enter Client account, Client contact email, External reference and Client notes when you have them. Result: the client workspace has a recognizable name, contact inbox and CRM reference before reports are shared.
  3. Choose Assign project when an existing project already belongs to this client, or leave No project yet when the client workspace is being prepared first. Result: project data is either attached immediately or stays ready for later assignment.
  4. Click Create client account. Result: the client appears in Client accounts with contact details, external reference and project count.
  5. In Client project, choose the client from the Client account selector and click Save when an unassigned project should move under that client. Result: scan, report, fix, handoff and monitoring badges are grouped under the correct client workspace.
  6. Review Client accounts and Client project status badges before starting scans or sharing reports. Result: client limits, project ownership and delivery state are clear before client-facing work begins.

Assign projects and review status

The Client accounts list is the source of truth for which client owns which project. If a project appears under the wrong client, correct the Client account selector before sharing a report, starting a new scan or sending remediation tasks.

Continue to white-label and report sharing

After the client workspace and project assignment are correct, continue to [Configure white-label controls](/docs/accounts/white-label-controls) so reports use the right agency brand. When the report is ready for delivery, continue to [Share client reports](/docs/accounts/share-client-reports).

Availability boundaries

Client account actions depend on agency role, plan eligibility, client limits and report-sharing state.

  • Agency account required means direct client accounts cannot create agency client workspaces.
  • Client limit reached means the current plan has no remaining client account slots; review agency allowances before adding another client.
  • Project belongs to another agency means it cannot be assigned from this workspace.
  • Unassigned project means the project can exist, but client report sharing and handoff status may be unclear until it is attached.
  • Client access boundary means one client workspace does not expose other agency clients, billing settings or unrelated reports.

Related documentation

Was this page helpful?

Feedback goes into the product documentation review queue.