Overview

Billing, Workspace, and Admin: plans, handoff access, and controls

Understand subscription plans, workspace permissions, and payment-adjacent handoff access without assuming every workspace has self-serve payment setup enabled.

High-level orientation page that explains structure and decision boundaries.

In this guide

Ownership and review discipline

Support
Last reviewed 2026-03-12Review cadence 30 days

Change signals to watch

  • send modal behavior changes
  • buyer signing flow updates
  • deal room experience changes
  • plan architecture updates
  • workspace permissions changes
  • billing and subscription policy updates

Operator guidance

What this means in QuoterAgent

Use this guide as the operating reference for Billing, Workspace, and Admin: plans, handoff access, and controls. It explains what this surface controls, what good execution looks like, and which teams should keep it trustworthy over time.

  • This guide covers the administrative areas that affect how QuoterAgent operates: subscription plan access, workspace-level controls, and payment-adjacent handoff availability when setup is configured. It does not assume every workspace can self-connect a payment processor from Settings.
  • Payment handoff should not be presented to clients until the workspace is configured for it. QuoterAgent keeps accepted proposal context visible so teams can move from proposal review into delivery and commercial next steps without relying on stale pricing or vague responsibilities.
  • Primary owners currently covering this area: Support.

What to do

Treat this as a working checklist, not background reading. Use it before you change settings, publish external material, or hand work to another operator.

  • Use this guide when preparing a workspace for real client delivery, reviewing paid-action access after the trial, or adding team members who need proposal controls.
  • Before relying on payment handoff in a client workflow, confirm it is enabled for the workspace. If it is not enabled, keep the proposal review and delivery handoff in QuoterAgent and complete payment steps through the process your team already uses.
  • Check whether payment handoff is enabled before sending a proposal that references it.
  • Confirm the plan supports the paid actions your team expects after the trial.

Where it shows up in the workflow

This guide matters most when work moves between setup, authoring, buyer delivery, and post-sign execution. Use the linked guides to follow the full path instead of solving one surface in isolation.

  • Payment-adjacent handoff connects to the accepted proposal, the current plan, and the workspace controls that are enabled. The buyer-facing value is simple: clients should review the sent version, and teams should know which next steps are available before delivery starts.
  • Review the related guide "Getting Started: workspace setup and first value" when this step depends on another surface.
  • Review the related guide "Sending and Signing: buyer-facing flow and acceptance confidence" when this step depends on another surface.

Common failure modes and risks

Most quality problems here come from drift: outdated setup, weak commercial boundaries, or teams skipping the review moment before customer-visible delivery. Use these signals to catch issues before they reach the buyer.

  • send modal behavior changes
  • buyer signing flow updates
  • deal room experience changes
  • Confirm payment handoff access before making it part of a client process.
  • Keep pricing, scope, and client responsibilities aligned before sending.

What this is

This guide covers the administrative areas that affect how QuoterAgent operates: subscription plan access, workspace-level controls, and payment-adjacent handoff availability when setup is configured. It does not assume every workspace can self-connect a payment processor from Settings.

  • Payment handoff: available only when payment setup is configured for the workspace and proposal flow.
  • Subscription plan: controls continued access to creation, generation, sending, export, and handoff actions after the trial.
  • Workspace access: manage who can create, review, send, and administer proposal work.

When to use

Use this guide when preparing a workspace for real client delivery, reviewing paid-action access after the trial, or adding team members who need proposal controls.

  • Before sending proposals that need payment handoff: confirm the handoff flow is enabled.
  • When a payment step is unavailable: check the workspace plan and configured handoff setup.
  • When adding a team member: assign their role before they attempt to send or execute proposals.

Why it matters

Payment handoff should not be presented to clients until the workspace is configured for it. QuoterAgent keeps accepted proposal context visible so teams can move from proposal review into delivery and commercial next steps without relying on stale pricing or vague responsibilities.

  • Confirm payment handoff access before making it part of a client process.
  • Keep pricing, scope, and client responsibilities aligned before sending.
  • Treat payment setup details as operator-managed unless your workspace has an enabled self-serve setup flow.

How it connects

Payment-adjacent handoff connects to the accepted proposal, the current plan, and the workspace controls that are enabled. The buyer-facing value is simple: clients should review the sent version, and teams should know which next steps are available before delivery starts.

  • Accepted proposal -> client review -> payment or next-step handoff when enabled.
  • Plan tier -> controls continued paid actions after the trial.
  • Workspace roles -> determine who can administer, review, and send proposal work.

Next steps

Before relying on payment handoff in a client workflow, confirm it is enabled for the workspace. If it is not enabled, keep the proposal review and delivery handoff in QuoterAgent and complete payment steps through the process your team already uses.

  • Check whether payment handoff is enabled before sending a proposal that references it.
  • Confirm the plan supports the paid actions your team expects after the trial.
  • Keep workspace roles current so the right people can review, send, and manage proposal handoff.

Related guides