Skip to main content

Team access & roles

Every member of your organization has a role. The role decides which AWS accounts they can see and what they can do there — view, connect, deploy, manage users. A new member has almost no access until you give them a role.

All of this is under the gear icon (top right) → System configurations:

TabUse it to
Role managementSee the built-in roles, and create your own.
Assign accessGive a person a role (adds them to your organization if needed).
Assignments listSee who has which role; Edit or Revoke it.
My capabilitiesSee exactly what you can do.

Built-in roles​

RoleWhat the person can do
RootAdminEverything, including upgrading ESP CloudHub. Given to the administrators named when ESP CloudHub was deployed.
AggregatorAdminRun the organization: add, connect and delete AWS accounts, deploy and upgrade products, add people and give them roles.
Client_ManagerConnect AWS accounts and deploy, read and delete products, on all accounts in the organization.
Rainmaker_SpecialistView accounts and deploy / read ESP RainMaker only, on all accounts in the organization.
Agents_SpecialistSame as Rainmaker_Specialist, for the Agents product.
AuditorRead-only: see accounts and products, change nothing.
CloudHub_OperatorESP CloudHub settings and user management only — no access to AWS accounts or products.

Need something narrower — for example, only some AWS accounts? Create a custom role (scenario 1).

Scenario 1 — Let someone deploy on only some AWS accounts​

Example: your organization has a Production and a Staging AWS account. A teammate should deploy ESP RainMaker to Staging only, and must not see Production.

Before you start: add both AWS accounts in ESP CloudHub. Connect Staging yourself — this role can deploy but not connect accounts.

1. Create the role​

Open Role management → + Create role and fill in:

Create custom role: Role name (1), Display name (2) and Description (3).

  1. Role name (ID) — e.g. Staging_Deployer (no spaces).
  2. Display name — e.g. Staging deployer.
  3. Description — what the role is for.

Leave Grant level at 40.

2. Choose what the role can do, and where​

Scroll down to Statement #1 (type Tenant & product):

Statement #1: the Staging account selected under Resources (1), Rainmaker selected under AllowedProducts (2), and the Live Policy Preview showing tenant, product and product on that one account.

  1. Under Resources, select only the Staging account (not All tenants).
  2. Under AllowedProducts, select Rainmaker.
  3. Under Actions, tick tenant:view, product:read and product:deploy.

Check the Live Policy Preview on the right, then click Create role catalog entry. The new role appears in the list.

Role Catalog with the new Staging_Deployer role (1).

3. Give the role to your teammate​

Open Assign access:

Assign access: the teammate's email (1), the Staging deployer role (2), and the policy preview.

  1. Enter your teammate's email.
  2. Choose Staging deployer under Role template.
  3. Click Create / invite & assign.

They now appear in Assignments list with the new role.

Assignments list showing the teammate with Staging_Deployer (1).

4. What your teammate sees​

When your teammate signs in, they see only the Staging account:

The teammate's console: only the Staging account is listed (1).

Under My capabilities, Tenant Account Scope shows the one account and Product Categories shows Rainmaker:

My capabilities for the teammate: Tenant Account Scope shows only the Staging account (1); Product Categories shows Rainmaker (2).

Why the matrix says DENIED

The Capability matrix at the top of My capabilities shows permissions across all accounts, so a role limited to one account shows Deploy products: DENIED there. The account-specific permission is shown under Tenant Account Scope.

To add more accounts later, click Edit next to the role in Role management (only your own roles can be edited). Everyone with the role gets the change.

Scenario 2 — Give someone read-only access​

Example: an auditor or manager should see the accounts and deployments, but change nothing.

Assign access → enter their email → Role template: Auditor → Create / invite & assign.

Scenario 3 — Let someone deploy ESP RainMaker on every account​

Assign access → Role template: Rainmaker_Specialist. For full control of the organization instead (including adding people), choose AggregatorAdmin.

Scenario 4 — Remove someone's access​

Assignments list → find the person → Revoke. To change their role instead, click Edit and pick another role. Changes take effect within about a minute.

Adding people​

ESP CloudHub you useHow a new person gets in
Espressif-hostedAsk them to sign up at espcloudhub.rainmaker.espressif.com first. Then add them with Assign access (their email), or send them your invite code and give them a role once they've joined.
Your ownThere is no sign-up. Add them with Assign access (their email). No email is sent, so set a temporary password for them with the AWS CLI (same command as resetting an administrator's password) and send it to them. They set their own password at first sign-in.
Who can give which roles

You can only give roles up to your own level — for example, an AggregatorAdmin can't make someone a RootAdmin.

Advanced: writing a role as JSON

In + Create role, Advanced JSON only lets you paste a policy directly. The role from scenario 1 looks like this:

[
{
"Effect": "Allow",
"Actions": ["tenant:view", "product:read", "product:deploy"],
"Resources": ["tenant:444455556666"],
"Conditions": { "AllowedProducts": ["Rainmaker"] }
}
]
  • Resources — tenant:* for all accounts, or tenant:<12-digit AWS account ID> for specific ones.
  • Actions — tenant:view, tenant:create, tenant:update, tenant:connect, tenant:delete, product:read, product:deploy, product:delete.
  • Conditions.AllowedProducts — optional; limits the role to Rainmaker, RMNG or Agents.
  • An explicit Deny always wins over an Allow; anything not allowed is denied.

On this page