Skip to main content

Clients and onboarding

A client is a SolveGRC organization your partner manages. It moves through a lifecycle (provisioning, onboarding, active, offboarding, archived), carries a service mode (fully managed, co-managed, advisory), and is served by your staff through delegated sessions rather than memberships.

The dashboard​

Portfolio Dashboard opens with five counters: total clients, active, onboarding, how many need attention, and how many delegated sessions are live across your partner right now. Four cards below summarize the work queue (open, overdue, at risk, yours), the evidence triage inbox, upcoming reviews, and the connector fleet, each linking to its page.

  • Portfolio health lists every client, worst first, with its overall health score and the compliance, evidence, risk, open-risk and member figures behind it. Health scores are snapshots: Refresh Scores recomputes them for every client from compliance coverage, evidence freshness, open and critical risks, recent activity and onboarding progress.
  • Attention is the queue of clients that trip a rule: compliance below 60%, stale evidence, onboarding stalled beyond 14 days, or open critical risks, each with a reason and an urgency.
  • Pipeline counts clients per lifecycle stage and, where packages are assigned, per package.
  • Heatmap shows compliance per client per framework, once any client has framework coverage.

The client list​

Clients lists every client with its lifecycle stage, service mode, industry, size, member and site counts, your internal reference, and risk profile. Filter by status and service mode or search by name. Administrators see New Client.

Creating a client​

New Client asks for the organization name and a slug (checked live for availability), the service mode, and optionally industry, company size, risk profile, your internal reference (a PSA ticket, say) and a primary contact email. Give a contact email and that person receives an administrator invitation to the new organization as soon as it is created.

Creation starts onboarding immediately and lands you on the wizard.

Onboarding​

The wizard runs seven steps in a fixed order, with a readiness meter at the top; you can revisit any step.

  1. Package: pick an active service package. It defines the modules the client's people are provisioned with.
  2. Template: deploy a published template pack to pre-populate the workspace. A pack can be deployed once per client.
  3. Permissions: provision module permissions for the organization's members from the assigned package. Members who join later are not covered by this step, so run it once the client's people have accepted their invitations.
  4. Contacts: invite the client's users as organization administrators, marking one as the primary contact. Pending invitations can be resent, copied as a link, or revoked from the same step.
  5. Integrations: not yet available in the wizard; skip it.
  6. Readiness: Calculate Readiness scores the client on seven checks, each worth a stated number of points: package assigned, template deployed, permissions provisioned, client contact invited (which counts only once someone has accepted), primary contact set, a framework activated, and controls created.
  7. Go Live: activates the client and begins service delivery. It needs a readiness score of at least 50%.

Every step except the readiness calculation requires an administrator.

The client page​

Opening a client shows its name, slug, lifecycle stage, service mode and risk profile, with the actions available to you:

  • Act as Client opens a delegated session into the client's workspace. Any member can use it, subject to their role and team assignment.
  • Start Onboarding or Continue Onboarding, depending on where the client is.
  • Invite User (administrators) adds a person to this client organization only. They get no access to your portal or to any other client.
  • Lifecycle (administrators) moves the client between stages: from provisioning to onboarding, from onboarding to active, from active to offboarding, from offboarding to archived or back to active. Archiving is the end of the line; an archived client cannot be opened in a session.

Four tabs: Overview (industry, size, primary contact, reference, counts, created date). Sites: the client's offices, branches, subsidiaries, data centers, cloud tenants, business units and plants. Sub-tenants (administrators): child organizations under this client, for regions or business units, created the same way as a client and linked under it. Teams: which of your teams are assigned to this client and, for administrators, the per-module access each team has here. See Members, teams and access.