Skip to main content

Roles

Every workspace starts with four roles:

Key differences

  • Owner — there is exactly one owner per workspace. The owner alone manages billing and can rename, transfer, or delete the workspace. To hand the workspace to someone else, see Transfer ownership.
  • Admin — admins can do almost everything the owner can: manage members, roles, outside collaborators, and projects. They can’t manage billing or change the workspace’s own settings. A workspace can have any number of admins.
  • Member — members see and work in every project in the workspace and can merge to staging. They can’t create projects or change project settings.
  • Restricted — restricted people can open every project and chat, but they only get read access to code and to your connected Odoo environments.

Custom roles

Owners, and anyone whose role can manage roles, can change these roles or create new ones on the workspace’s Roles tab. A role decides how far someone may go with code and connected Odoo, and whether they can see usage, manage connections, roles, members, or projects, and delete & transfer projects. Billing always stays with the owner. You can only manage roles that sit below your own in the list.
”Delete & transfer projects” always includes “Manage projects” — whoever can move a project out of a workspace can bring one back in.

Outside collaborators

Sometimes someone outside your workspace — a contractor, a client, a consultant — needs to work on a single project. Instead of making them a member (which opens every project), add them to just that project:
  1. Open the project and go to Settings → People & access
  2. Under Outside collaborators, click Add collaborator
  3. Enter the email address of their CodeCobra account, pick their role for this project, and click Add
A collaborator can open that project and work in it with the role you gave them, but they can’t see any other project in your workspace and they aren’t listed as a member. Anyone who can manage members can remove a collaborator at any time, and a collaborator can leave a project themselves.
Outside collaborators are only available on workspace projects, and their usage is billed to the workspace. To share a personal project, move it to a workspace first.
Collaborators need an existing CodeCobra account. If the person hasn’t signed up yet, ask them to create an account first, then add them by the same email address.

Invite members

  1. Open your workspace and go to the Collaborators tab
  2. Click Invite
  3. Enter one or more email addresses — press space or enter after each one
  4. Choose a role for them. You can only give out roles below your own, and never Owner.
  5. Optionally tick Require 2FA before joining
  6. Click Send Invite
Invitees receive an email with a link to accept. Invitations expire after 7 days. Pending invitations are listed on the Collaborators tab, where you can copy an invite link or revoke an invitation that hasn’t been accepted yet.
An invitation can only be accepted by a CodeCobra account with exactly the email address it was sent to. Someone else who gets hold of the link can’t use it.

Accept an invitation

You can accept from the email or from inside CodeCobra:
  • From the email — open the link. If you aren’t signed in, click Sign In first, using the account with the invited email address. Then click Accept Invitation.
  • In CodeCobra — open Workspaces. Invitations waiting for you are listed under Pending invitations; click Accept (or Decline).

Manage members

Anyone whose role can manage members can, for people whose role is below their own:
  • Change a member’s role — on the Collaborators tab, click the member’s role and pick another
  • Remove a member — they lose access to every workspace project immediately, unless they were separately added to a project as an outside collaborator
Removing a member is immediate. Tasks they created stay in the workspace’s projects, but they can no longer open them.
To leave a workspace yourself, click Leave at the top of the workspace page. The owner can’t leave until they’ve transferred ownership.

Transfer ownership

The owner can hand the workspace to someone who is already a member:
  1. If they aren’t a member yet, invite them and wait for them to accept
  2. Open the workspace’s General tab and find Ownership & deletion
  3. Next to Transfer ownership, click Transfer
  4. Pick the new owner and click Transfer
You become an admin, and the new owner gets billing. The workspace keeps its projects, members, and balance. Cards you added stop being charged for the workspace, so the new owner should add their own under Settings → Billing. If the new owner’s GitHub account can’t reach some of the repositories linked to the workspace’s projects, you’ll see them listed before the transfer goes through. Transferring anyway blocks the team from cloning and pushing to those repositories until the new owner is given access on GitHub.

Delete a workspace

The owner can delete a workspace from the General tab: next to Delete workspace, click Delete and type the workspace’s name to confirm. Every member is removed, and the workspace’s projects move to the owner’s personal account.
A workspace that still has credit can’t be deleted. Contact support to move or refund the balance first.

Next steps

Workspaces

How workspaces, members, and projects fit together.

Create a project

Add projects to your workspace.