Team, roles and sign-in
Who can model, run, approve and push in TrueUpp: the admin, approver and analyst roles, invitations, required two-factor sign-in and four-eyes.
On this page
Every TrueUpp user belongs to one workspace and has one role. Roles separate who models contracts, who approves numbers and who changes connections. Everyone signs in with two-factor.
Roles
- Analyst models contracts, imports usage, starts runs and reads everything.
- Approver does everything an analyst does, and also approves and pushes lines and resolves exceptions.
- Admin does everything an approver does, and also manages connections, workspace settings, the team, the plan and deletion.
The person who creates a workspace is its first admin.
What each role can do
| Action | Analyst | Approver | Admin |
|---|---|---|---|
| See contracts, runs, lines, traces, exceptions, statements and the audit log | Yes | Yes | Yes |
| Download CSV exports | Yes | Yes | Yes |
| Create, import and amend contracts; map billing customers; edit clause references; archive and restore | Yes | Yes | Yes |
| Import usage and billed amounts, void imports, attach or ignore unmapped usage, start a warehouse sync | Yes | Yes | Yes |
| Start a Salesforce CPQ sync | Yes | Yes | Yes |
| Start a run or re-run; generate a statement | Yes | Yes | Yes |
| Approve, reject, hold and release lines | Yes | Yes | |
| Push approved lines to Stripe or NetSuite | Yes | Yes | |
| Resolve, assign and suppress exceptions | Yes | Yes | |
| Create and revoke statement share links | Yes | Yes | |
| Connect or disconnect Stripe, NetSuite, Salesforce CPQ and warehouse sync; create usage webhook tokens | Yes | ||
| Change workspace settings: name, logo, currency, close day and time zone, four-eyes, statement footer, Stripe collection method, billing system, alerts | Yes | ||
| Invite people, change roles, remove people | Yes | ||
| Choose or change the plan, manage payment details | Yes | ||
| Delete a contract | Yes |
If someone tries an action their role doesn't allow, TrueUpp refuses it and names their role, for example "Your role (analyst) can't do that."
Admins and approvers receive the emails meant for approvers: the scheduled close summary and, on Growth, discrepancy and commit-pacing alerts.
Inviting people
- An admin opens Settings › Team, enters the person's email, picks a role (analyst by default) and clicks Send invite.
- TrueUpp emails an invitation to join the workspace. The invitation link is also shown on screen, so you can send it yourself.
- The person opens the link, creates an account with the invited email address, and clicks Join workspace. The address must be verified and must match the invitation.
- Before they can see any data, they turn on two-factor sign-in.
Invitations expire after 7 days. Pending invitations are listed on the Team page with their role and expiry date. An account belongs to one workspace, so someone who is already in another workspace can't accept with that account.
Required two-factor sign-in
Nobody reaches any data screen without two-factor sign-in, whatever their role. A user who signs in without it is sent to the Two-factor sign-in page until it is on.
- On that page, under Security, add an authenticator app.
- Save the backup codes it shows you, somewhere other than the device with the authenticator app.
- Reload the page. It confirms that two-factor is on and lets you continue.
Backup codes
The backup codes are how you sign in if you lose the device with your authenticator app. Keep them somewhere safe and separate from that device.
Four-eyes approval
With four-eyes on, the person who pushes lines must be someone other than the person who approved them. TrueUpp refuses the push otherwise, with "Four-eyes is on: someone other than the approver has to push." It applies to pushes to Stripe and to NetSuite.
Four-eyes is off by default. An admin turns it on in Settings › General. With it on, you need at least two people who can approve or push.
Changing a role
An admin picks the new role next to the person on Settings › Team and clicks Save. The change applies to their next action. A workspace always needs at least one admin, so the last admin can't be changed to another role.
Removing someone
An admin clicks Remove next to the person on Settings › Team. Their access ends straight away. You can't remove yourself, and you can't remove the last admin.
Removing someone doesn't remove their history. Every approval, push and change they made stays in the audit log under their email address.
Invitations, role changes and removals are all recorded in the audit log, with who made them and when.