Everything in CloudBurn Platform belongs to a workspace: connected AWS accounts, scan results, the linked GitHub installation, and the plan that pays for them. Members of a workspace share all of it, so a scan one teammate runs is visible to everyone, and an AWS account connected once serves the whole team.
You get a personal workspace when you sign up. Joining another team's workspace happens through an invitation; switch between the workspaces you belong to from the Workspace menu in the dashboard header.
Roles
| Role | Can do |
|---|---|
| Member | View and run optimization scans, use the dashboard tools |
| Admin | Everything a member can, plus connect, verify, rename, and remove AWS accounts, manage members, and change repository slots |
| Owner | Everything an admin can; designated billing owners also manage plans and billing |
The workspace's billing owner cannot be removed or demoted, and only an owner can promote someone else to owner.
Inviting and managing members
From Settings → Workspace:
- Workspace name is shown to everyone with access; owners and admins can change it.
- Invite a member takes an email address and a role (Member or Admin), then emails an Accept invitation link. The invitee needs a CloudBurn account with a verified email; if they are not signed in, the link asks them to sign in first. Pending invitations stay listed under Members with a Resend option.
- Members lists everyone with access and their role. Removing a member takes effect immediately: they lose access to the workspace and its AWS accounts, but nothing is removed from AWS.
What's next
| Read this | To learn |
|---|---|
| Connect an AWS account | Add an account the whole workspace can scan |
| Plans and billing | What the workspace owner manages |
| Set up PR cost estimation | Link the GitHub App and choose repositories |