Running RevTech: access, teams and credits
The administrative half — company settings, integrations, roles, users, billing and credit usage. Set up in the right order, then reviewed on a rhythm.
One entry, a page of cards
Admin is one entry in the sidebar, and it opens a page of cards: Company Settings, Users, Roles & permissions, Billing & Plans, Credit Usage and Integrations. Each card opens its own section, and each is shown only to people who can open it, so a user administrator and a billing owner see different pages. Someone who can open none of them has no Admin entry at all.
Two things people look for elsewhere. Company Settings is a card here, not an item in the account menu. Teams is not here at all: it lives in Goals & Targets, under Team Setup.
The order of setup
The Admin cards are where you decide how RevTech sees your business, and the sequence is not arbitrary. Company Settings first. It opens on the fiscal calendar — default currency, fiscal-year start month and year — because that drives how every forecast, quota and KPI gets bucketed; identity, branding and regional defaults follow. Then connect the CRM from Integrations, because everything else assumes it. Then roles, then teams, then invite people.
Doing it in this order means each decision is made once. Inviting people before roles are customized means a round of reassignment; setting targets before teams exist means orphaned numbers.
Integrations: the connection everything rests on
The Integrations card lists HubSpot and Salesforce with each one’s status and, once connected, when it last synced. HubSpot is self-serve: Connect starts the authorisation, which you complete in HubSpot, and once connected the gear beside it shows the scopes it was granted. Its controls belong to RevTech administrators; anyone else sees it marked Admin-managed.
Salesforce is set up with the RevTech team rather than self-serve. Get setup help opens a support request over the page, already titled, and the team takes it from there. The use case Connect the CRM and keep it current covers the whole job, including what to check first when a number looks stale.
- Connect starts the HubSpot authorisation
- Reconnect appears when the connection needs attention, and authorises again
- Deactivate pauses syncing but keeps the authorisation; Re-activate resumes it without a sign-in
- Disconnect revokes access after a confirmation; connecting again means authorising again
Roles: scope first, then sections
Roles live on the Admin page, behind the Roles & permissions card. RevTech ships eleven default roles modelled on a real B2B revenue org — Admin, RevOps, Finance, Sales Manager, Seller, Marketer, Marketing Leader, CS Rep, CS Leader, Executive, Observer. Most teams clone these rather than inventing from scratch, which is the right instinct. The role also decides what each person sees on Home: Seller gets the Sales layout, Admin the RevOps layout, Finance and Observer the Executive layout, and so on.
Inside a role, scoped record access is the setting to get right first, because it shapes everything below it. Set it per object: All is tenant-wide, Team is records owned by the user's teams, Own is self-owned only, None hides the section. Sellers usually run on Team, executives on All. Then grant section access: read shows a section, write adds editing, and the smallest set that lets the role do its job is the correct one.
The editor shows the consequence of each switch in reports. Under a permission it lists the reports that permission opens, whether or not it is granted, and at the top it lists every report the role can open, grouped by category, updating as you change switches. When someone asks why their manager cannot see Deal Risk, this is where you find the answer: the role is missing View Pipeline.

The permissions worth pausing on
The administration toggles — Manage Users, Roles, Teams, Billing — are governance powers, and most non-admin roles need none of them. Manage Roles in particular is a real escalation: a role holding it can edit every other role, including the ones constraining it.
Analyst access has its own gate. Toggling it opens a picker for exactly which questions a role may run, and leaving the selection empty grants all of them. Three to five high-signal questions per persona is more useful than everything. A library of forty questions with no curation is one nobody navigates.
Users, and off-boarding safely
Users, the card beside Roles & permissions on the Admin page, controls who runs revenue inside RevTech; every report, agent and CRM scope downstream is gated by what is set here. Status, source and last login together tell you who is actually working this week, who is pending, and who has drifted. Source also tells you provenance: a healthy workspace is mostly real GTM people from the CRM plus a small set of native admins.
Archiving soft-deletes a user and revokes their tokens while preserving history, and it can be undone. Consequential changes ask twice and show the from-and-to state. The "only admin" and "editing yourself" guards exist to block the two lockout failure modes, which is worth knowing before you try to work around them.
- Bulk invites share one role and one team — keep batches small and homogeneous
- Pick the role first and the team second
- Pilot a new custom role with one or two users before expanding it
Credits: the balance and the burn
Billing & Plans shows the credit balance, what is reserved for in-flight runs, and consumption against your commitment, with thresholds at 80%, 90%, 100% and 105% each carrying their own treatment. Auto top-up is optional and fully specified by you: whether it is on, the balance that triggers it, and how much each top-up buys.
Credit Usage is the diagnostic half — run-level visibility into which workflows, teams and agents are consuming credits, with a trailing twelve-month view by team and a searchable run list for investigating failed or cancelled runs. Its most useful output is spotting the one or two features that dominate the bill, and then deciding whether that concentration is intentional or wants a guardrail.

The quarterly review
None of this is one-time setup. Put a thirty-minute access review on the calendar each quarter and spend it on this page: roles that have accumulated permissions, admins nobody remembers granting, archived users still holding assignments, and custom roles with zero users that should be retired.
The role model only stays useful when it gets revisited. A permission structure designed carefully in month one and never opened again is, by month twelve, a description of an organization that no longer exists.
What to take away
- Admin is one sidebar entry and a page of cards. Each card shows only to people who can open it.
- Order matters: company settings, then CRM, then roles, then teams, then people.
- Scoped record access shapes every other permission in a role. Set it first.
- Granting Manage Roles is a real escalation — that role can edit every other role.
- Archive, do not delete. History is preserved and lockout guards exist for a reason.
- Credit usage tells you which one or two features dominate the bill. Decide whether that is intentional.
Put it to work
Jobs this page is behind
- Forecast and planShow what the capacity was spent on“I want to answer, with numbers, what we got for running agents.”
- Governance and administrationGet the tenant working in week one“I want to get our workspace set up properly, in the right order, in the first week.”
- Governance and administrationConnect the CRM and keep it current“I want to connect our CRM and be able to tell whether the data is current.”
- Governance and administrationGive each role exactly its access“I want to give every role the access it needs and nothing beyond it.”
- Governance and administrationNever be surprised by the bill“I want to know what agent work costs us and keep it predictable.”
See how the work gets done.
Explore how agents prepare work across your revenue teams, and how people review it, guide it and decide what happens next. Fictional data. Real product.
Explore the demo