Teams and roles
Create workspaces, invite members, and use roles so clients and colleagues see only what they should.
8 min read
By default everything you create belongs to your personal account. That works perfectly for one person managing one site.
Teams turn Cache Rocket into a multi-tenant workspace product: separate containers of warmers, hostnames, alerts, and CDN integrations, each with their own members and permissions.
Teams are managed under Account → Teams, and are available on plans that include the feature — commonly Business.
When you need a workspace
| Situation | Why teams help |
|---|---|
| An agency managing client sites | One workspace per client. Nothing bleeds between clients, and you can grant a client read-only access to their own workspace without exposing anyone else's. |
| An in-house platform team | Several product squads share warmers with roles that match responsibilities. |
| A consultancy handing over | Give stakeholders Viewer access so they can see results without changing configuration. |
| Separating finance from engineering | Whoever handles invoices does not need — and should not have — write access to warmers. |
Creating a team
- 1
Open Account → Teams
Enter a name — usually the agency, client, or business unit — and click Create.
- 2
Understand what moves
When you create your first team, existing warmers, hostnames, alerts, and CDN integrations are moved into it. You can reassign them later from each warmer's Team field.
- 3
Invite members
Enter an email address, choose the team, pick a role, and send the invitation.
- 4
Switch workspace to work in it
Use the workspace selector in the sidebar. Everything you see and create belongs to the active workspace.
Check the active workspace before creating things
A warmer created in the wrong workspace is invisible to the people who need it. The sidebar selector always shows which workspace you are in — glance at it before you build.
The roles
| Role | Can do | Cannot do |
|---|---|---|
| Owner | Everything, including deleting the organisation | — |
| Admin | Full access to all resources and members | Delete the organisation |
| Developer | Manage warmers, hostnames, alerts, CDN and integrations | Anything billing-related |
| Finance | Manage billing and subscription; read warmers | Create or change warmers and settings |
| Viewer | Read-only access across the workspace | Change anything |
Navigation adapts to the role. Someone with Finance access does not see warmer editing tools, and a Viewer sees no write controls at all — the interface reflects their permissions rather than showing buttons that fail.
Choosing roles well
- Developer is the right default for engineers and site managers. It covers everything operational without exposing billing.
- Finance suits an accounts person who needs invoices but has no reason to touch configuration.
- Viewer is ideal for clients and stakeholders who want to see that warming is working.
- Admin should be rare. Give it to the people who genuinely administer the workspace.
- Owner stays with whoever is ultimately responsible for the account.
The agency pattern
One workspace per client. Your own staff get Developer. The client contact gets Viewer on their workspace only. Each workspace has its own alert endpoint posting into that client's channel, so failures reach the right people automatically.
Assigning warmers to teams
Each warmer has a Team field controlling which workspace owns it. Only members of that team can see and manage it. Use it to move a warmer between workspaces — for example when onboarding a site you previously ran from your personal account.
Common questions
- Which plan includes teams?
- Plans with the teams feature, commonly Business. If Teams is missing or shows an upgrade notice, your current plan does not include it.
- What happened to my existing warmers after creating a team?
- They were moved into the new team, along with hostnames, alerts, and CDN integrations. Reassign individual warmers from their Team field if you want them elsewhere.
- Can one person belong to several workspaces?
- Yes, with a different role in each. Switch between them using the sidebar selector.
- Do hostnames need verifying separately per workspace?
- Hostnames belong to the workspace that owns them. Verify a client's hostname inside that client's workspace so its warmers can use it.
- Can a client see other clients?
- No. Membership is per workspace, and a member sees only the workspaces they belong to.