Team, roles and access
People, teams, requests, access tokens, access reviews, app access, offboarding, release rules and personas: everything on the Team page.
Team is where an organisation manages its people and who may do what. What you see depends on your role: members see People and their own tokens; admins and Owners see the management tabs.
Tab | What you do there |
|---|---|
People | Everyone in the organisation with their role and teams. Invite people, Add person; a person's menu has change role, reset sign-in, remove from the organisation, start offboarding. Pending Invitations are listed here too |
Teams | New team, add people, set each person's role in the team. A team has its own page with its members and projects |
Requests | Access requests, offers and ownership transfers. Request access to something; requests you can decide show Approve and Decline; History keeps the outcome |
Access tokens | Personal tokens ( |
Access reviews | Confirm who should keep access to your organisation's projects and resources |
App access | Which parts of REM CloudHub each audience sees ("Nothing ticked: everyone in the organisation sees it"). Check access answers why someone can or cannot do something |
Offboarding | People who are leaving: their last day, what is handed over and when their personal secrets are revoked |
Release rules | What a production deploy must pass (Owners; see Projects) |
Personas | Groups of people who do not see certain apps, pages, tabs or fields, for a simpler console. Personas only hide; they never grant anything |
Roles
Role | In short |
|---|---|
Owner | Runs the organisation: plan and billing, people, teams, rules, connectors |
Team admin | Manages their team's people and decides requests for its resources |
Member | Creates and works on their own and shared projects, jobs and resources |
Inside a project, job or resource, people and teams get Viewer, Collaborator or Admin. Sharing uses the Share panel on each item: Who can see it (personal, one team, several teams or the whole organisation) and Give access with an optional end date. You can only grant what you hold.
Access tokens
Scripts, CI pipelines and AI clients use tokens instead of your sign-in.
Personal access tokens (
qchp_...): Create token, give it a Name ("say where it is used, e.g. deploy script"), an end date, and optionally Bind it: Only for project, an App type, or Allowed sites (one origin a line). It can do what you can do, until it ends or you revoke it. The value is shown once.Service accounts (
qchsa_...): accounts programs use instead of a person. New service account (a unique Name such asbilling-sync, what it is for, the owner), then open it and New token. Each token is shown once; revoke one that might have leaked.Product tokens: the organisation's tokens for products such as REM Vibe Coder (names and prefixes only).
For how to use tokens, see the developer docs.
Removing someone
From their menu on People: removing them takes every role they hold in the organisation; their account stays and an admin can add them again. Reset sign-in ends every open session. For a planned departure use Offboarding, which hands over what they own and shared before access ends.