Introduction to Good Sign CPQ Admin

Audience: anyone responsible for setting up or maintaining Good Sign CPQ for their organisation — typically admin or power users. Scope: orientation. What CPQ is in Good Sign, where the admin work happens, and where to go for each piece. Detailed how-to guidance lives in the linked guides; this document positions them.

1. What Good Sign CPQ is

CPQ stands for Configure, Price, Quote — the process by which a salesperson assembles a tailored offer for a specific customer from a defined product catalogue, with the right pricing applied, and produces a quote document for the customer to sign.

Good Sign CPQ extends the core Good Sign billing platform with the configuration and quoting layer that sits in front of it. The same product catalogue, pricing rules, and customer organisations that drive Billing also drive CPQ — so a price change, a new product, or an updated customer org becomes immediately available to salespeople without a separate sync.

CPQ in Good Sign is built around three artefacts that admins maintain:

Forms — the structured selection screens salespeople use when configuring a quote. Each form defines the products available, how they are grouped into sections, the selection rules (mandatory, single-choice, plan), and the runtime settings (pricing org, language, permissions, template, e-signing).
Templates — the reusable document texts (introductory paragraphs, legal clauses, payment terms, logo) that are applied to the quote document when it is exported. Introduced in Release 2026_2.
CPQ Settings — environment-level configuration that applies across all forms and templates (currency defaults, document conventions, integration hooks).

Together these define what salespeople can quote and how quotes look when they reach the customer.

2. Two surfaces — admin and client

Good Sign CPQ has two distinct user-facing surfaces, used by different roles:

Surface	Used by	What it does
CPQ admin (inside Good Sign Billing)	Admins, power users	Build and maintain forms, templates, and master settings. Manage users and rights. Lives under Settings → CPQ in Billing
CPQ client	Salespeople, customer success, other quote-producing roles	Configure quotes from the activated forms and produce quote documents for customers. A separate UI, designed for the sales workflow

The two surfaces share users, organisations, products, prices, and rights — all maintained in Billing. There is no separate CPQ user database or product catalogue.

The rest of these admin guides describe the admin surface in Billing, not the sales-side workflow. The CPQ client is documented separately for sales users.

3. What an admin does in CPQ

The admin work breaks down into a handful of recurring tasks, each with its own guide:

Task area	Guide
User access — adding users, assigning rights, checking who can see what	CPQ User Management
Building selection forms — products, sections, selection rules, activation settings	CPQ Forms — Admin Guide
Maintaining quote-document content — introductory text, section blocks, logo	CPQ Document Templates — Admin Guide (new in Release 2026_2)
Environment-wide defaults — pricing, numbering, contracts, e-signing	CPQ Settings (Master Settings)
Orientation to where everything lives	CPQ Admin User Interface Overview

These are the documents that this introduction sits at the head of.

4. Who maintains what

Good Sign CPQ is rarely operated by a single role. The typical split:

CPQ admin / power user. Builds and maintains forms, templates, and master settings; manages CPQ user access. Spends most of their time in Settings → CPQ in Billing.
Salesperson. Uses the activated forms to configure quotes for customers in the CPQ client. Doesn’t touch admin pages.
System administrator. Manages the underlying Good Sign environment — billing organisations, products, prices, integration hooks. May also be the CPQ admin in smaller teams; in larger setups, a separate role.

User-rights profiles (e.g. CPQ Admin, CPQ Client) are typically used to group the permissions for each role together — but profile names and contents are environment-specific. See CPQ User Management for how to check and assign rights in your environment.

5. How CPQ talks to the rest of Good Sign

CPQ does not have its own data store. Everything CPQ uses lives in Good Sign Billing:

Products that appear in forms are Billing products.
Prices applied during configuration come from Billing pricing.
Customer organisations are the same organisations used for billing and invoicing.
Users and rights are the same identities used to sign in to Billing.

Quote outputs flow back into Billing too: once a quote is approved and accepted, the resulting contract and the invoicing that follows are handled by Billing. The CPQ artefacts (forms and templates) shape what the customer sees and signs, but the data path is Billing → CPQ admin → CPQ client → Billing.

This shared-foundation design means a change to a Billing product or price affects CPQ immediately, with no manual sync. It also means that changes to a CPQ form or template do not, by themselves, change pricing or products — they only change what salespeople can pick from and what the quote document looks like.

6. Where to go next

If you are setting up CPQ for the first time, work through the guides in this order:

CPQ Admin User Interface Overview — orientation to the navigation, where each piece lives [link].
CPQ User Management — make sure the right people have the right rights before you build anything [link].
CPQ Forms — Admin Guide — build the forms salespeople will use [link].
CPQ Document Templates — Admin Guide — set up the quote-document content that the forms link to [link].
CPQ Settings — environment-wide configuration; visit when you need to adjust defaults [link].

If you are maintaining an existing CPQ setup, you can jump directly to the guide for the area you need to change.