Billing
Review subscriptions, seats, plan controls, and billing-management actions from the Billing Dashboard.
Use this settings state to understand which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.
Learn the system by following the product states.
Use the screenshots as the primary map: start with the full context, trace the connected workflow, inspect the focused UI, then compare against the completed operating state.
Visible controlAccess or policyOperational effectUse this settings state to understand which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.
Summary
Review subscriptions, seats, plan controls, and billing-management actions from the Billing Dashboard.
Concepts covered
Step breakdown
- Open BillingStart in the Billing section of the Admin control center.
- Inspect the real controlsIdentify the visible fields, buttons, switches, tables, and menus before changing configuration.
- Connect the setting to operationsUnderstand which user access, customer memory, developer access, usage, billing, or data-model behavior this setting affects.
What this screen does
Billing shows the commercial state of the workspace. The captured dashboard includes plan cards, renewal context, seats, credit usage, Upgrade, Manage seats, Cancel subscription, and View more.
This is an operational admin screen, not a marketing pricing page. It helps owners understand what the workspace is subscribed to and how many seats or credits are being used.
What each control changes
View more opens deeper billing management. Upgrade changes the plan path. Manage seats adjusts seat allocation. Cancel subscription starts cancellation for the relevant product plan.
Use Billing before expanding rollout to more teams so subscription and seat state match the operational plan.
Operational outcome
Billing clarity prevents deployment surprises: the workspace has enough seats, the right plan, and a visible path for account owners to manage changes.
Operational playbook
Use Billing as part of the Frontline Admin Billing operating loop: inspect the current product state, confirm the source context, and decide what should happen next.
The goal is not to memorize screens. The goal is to understand how the product surface supports repeatable work, AI assistance, and accountable handoff.
Best practices
Start with the operational job before changing configuration. Name the owner, define the trigger or source context, and decide how the result should be reviewed.
Prefer narrow, inspectable setups over broad automation. Teammates should be able to explain why the system took an action from the visible product state.
Troubleshooting
If the result does not match expectation, check the source context first, then permissions, connected integrations, required fields, workflow logs, and any AI-generated output used by downstream steps.
When in doubt, compare the latest product state with the related record, activity, or workflow execution so debugging starts from evidence rather than guesswork.
FAQs
What does Billing control?
Review subscriptions, seats, plan controls, and billing-management actions from the Billing Dashboard.
Who should use this page?
Workspace admins, implementation owners, and operators responsible for configuring access, account behavior, developer integrations, or the data model.
How should this page fit into onboarding?
Use it to understand the product surface, inspect real UI states, and connect the concept to daily operating workflows before configuring production behavior.
What should I verify before using this in production?
Verify ownership, permissions, source context, failure behavior, and the handoff path so teammates can trust what the system does next.