Set up your account & team
The first things an administrator does: get into the portal, know which environment you’re in, and bring your team in with the right roles. (Admin)
Sign in
Section titled “Sign in”Open the Provision Portal and sign in with the account you created during onboarding. After sign-in you land on the first page your role can see — for an administrator that’s the Dashboard.
Know your environment
Section titled “Know your environment”Under Settings → Environments you’ll see every environment under your account — your production environment and, if you’ve created one, a sandbox. Each row shows its identifier, name and URL.
Use a sandbox to model the catalog and rehearse a flow without touching production. From Environments you can provision one sandbox per account, once a production environment exists. Switch environments by opening the environment’s URL.
Invite your team
Section titled “Invite your team”People are managed under Customers → Users.
- Open Users and create a user — give them an email and name.
- On the new user’s User Details tab, open the User Roles card and switch on the role they need (see below).
- Save. The person is invited and signs in with their own credentials.
You can later deactivate or approve/block an account from the same page. To find disabled accounts, filter the list to inactive users. Passwords and MFA are handled by the sign-in identity provider’s own recovery flow, not from the portal.
Assign roles
Section titled “Assign roles”The portal has a fixed set of four roles — pick the least-privileged one that lets the person do their job.
| Role | Give it to | They can |
|---|---|---|
| Administrator | Owners and operators | Everything, including Settings and Compliance |
| Sales | Account execs | Create and publish entitlements, manage customers, issue codes |
| Support | Support agents | Renew, top up credits, release activations, approve/unblock users |
| Viewer | Stakeholders | Read-only dashboards, reports and record browsing |
A few rules worth knowing:
- Roles expand into scopes at sign-in. Changing someone’s role takes effect at their next sign-in — the role card says so.
- The vocabulary is fixed. The role card is a set of switches, not a text box; there’s no custom-role builder.
- Seats and the granular-role gate. Administrator and Sales are administrator seats and count against your plan’s portal-user cap. The Sales, Support and Viewer roles require the role-based permissions feature — if your plan doesn’t include it, those switches are disabled with an upgrade hint and everyone is an Administrator.
What you can’t change
Section titled “What you can’t change”You can’t invent new roles or hand-edit individual scopes per user beyond the four personas. If the four don’t fit, the lever is the plan (to unlock granular roles), not a custom role. See Administer access & settings for API clients and the rest of Settings.