Skip to main content

Packages, templates and branding

Three settings shape what a client receives from your partner: a service package defines the modules and limits a client gets, a template pack bundles content to deploy into a client, and branding decides whose name the client sees on the platform.

Service packages​

Packages lists what you sell: each package with its tier, module count, how many clients are on it, its limits, its monthly price and its status. Administrators create packages and clone existing ones.

A package has:

  • A name and slug, a description, a tier (starter, standard, professional, enterprise, custom) and a service cadence (weekly, bi-weekly, monthly, quarterly, annual).
  • Included modules, chosen from the platform's active modules, grouped by category so a whole category can be toggled at once. This is the list a client on the package is provisioned with during onboarding.
  • Limits: maximum users, maximum environments and monthly AI credits, each blank for unlimited.
  • Service terms: whether the package includes a quarterly business review and vCISO service.
  • A base monthly price, which is informational: it describes the package and does not by itself bill anyone. Billing runs from contracts.

Packages are created active. Clone copies one under a new name and slug so you can vary it. A package is attached to a client during onboarding, where it drives which modules the client's people are provisioned with.

Template packs​

Templates lists reusable content bundles: each pack with its type, version, item count, how many clients it has been deployed to, the package it is linked to, and whether it is a draft or published.

A pack has a name and slug, a description, a type (general, industry specific, framework specific, compliance starter, BCM starter, audit readiness), an optional target industry, and an optional link to a service package; linked packs are recommended to clients on that package. The items a pack carries are policies, control baselines, framework configuration, evidence checklists, questionnaires, risk defaults, report configuration and automation rules.

Packs are created as drafts. Administrators publish a draft, which makes it deployable, and clone a pack to start a new version from it. Adding items to a pack and deploying it into a client are not yet available from the portal; SolveGRC sets those up with you today.

Branding and white-label​

Branding (Settings) controls how your clients see the platform. It applies to every client dashboard your partner manages, not to the MSP Portal itself.

Three modes:

  • Platform default: SolveGRC branding.
  • Co-branded: your logo and name, with a "Powered by SolveGRC" line you can reword.
  • Full white-label: your branding only.

Alongside the mode you set the company name, a platform name (what the product is called inside your clients' dashboards), logo URLs for light and dark mode, a favicon URL, a primary color, and a support email. Assets are referenced by URL rather than uploaded. The preview at the top of the page shows the result as a client's sidebar would render it. Only administrators can save.

A client's dashboard picks up the partner's branding automatically; a client organization may carry overrides of its own on top.