All articles

Getting Started

What is CICDoo "Getting started: the onboarding wizard" The Dashboard and Infrastructure Map

Concepts

Production, staging and development stages Domains, subdomains and SSL Odoo versions and editions (Community vs Enterprise) Workspaces and team collaboration

Servers

Adding a server Server domains and DNS Using a load balancer "Server actions: deploy, logs and charts"

Projects & Git

Creating a project Connecting GitHub Connecting GitLab Branches and instances

Instances & Console

Creating an instance Restarting, stopping and removing an instance Merging branches between stages Web IDE and remote access Instance settings explained Deployments and the job queue

Monitoring & Backups

Monitoring your instance Backups and restore Alert notifications (email and SMS)

Workspaces & Permissions

Inviting workspace members Member permissions and resource access A member cannot see or use a resource

Account & Security

Two-factor authentication (2FA) Profile and integrations settings Passwords and account recovery

Billing & Plans

"Plans: Free, Pro and Enterprise" Upgrading and managing your subscription What happens when you hit a plan limit

Support & Tickets

Opening a support ticket Getting help from the CICDoo team

Troubleshooting

"Troubleshooting: cannot connect a server" "Troubleshooting: a deployment failed" "Troubleshooting: my instance is down or slow" "Troubleshooting: domain or SSL problems"

Workspaces & Permissions

Member permissions and resource access

How the member permissions modal works, including the Member and Admin roles, resource access lists, and per-feature permission toggles.

Opening the permissions modal

Go to Settings, open the Workspaces tab, and find the member in the Members card. Click the shield icon next to their name. This opens the Member Permissions modal, where you control what that member can access and manage in your workspace.

The workspace owner always has full access and is not restricted by any of these settings.

Role: Member or Admin

At the top of the modal is a Role selector with two options:

  • Admin: admins have full access like the owner. They bypass all permission and resource access checks, and the other settings in the modal are ignored for them.
  • Member: members are restricted by the resource access lists and permission toggles below.

Resource Access (which things they can use)

For members, the Resource Access section decides which specific resources they can work with. It has three lists, each with a search box and Select all / Deselect all links:

  • Projects
  • Instances (each shows its project name)
  • Servers

Tick the items the member should be able to access. If a list is left empty, the member has no access to that type of resource. Save with the Save Permissions button.

Feature permissions (what they can do)

Below Resource Access are permission toggles grouped by area:

  • Servers: view and manage servers, plus sub-permissions to add servers, edit server settings, deploy servers, and delete servers.
  • Projects and Console: view projects and access the console, plus sub-permissions to create projects, edit project settings, and delete projects.
  • Instances / Console: granular instance operations, including create instances, restart / upgrade, stop instances, create backups, merge branches, remove instances, connect as user, modify settings, access the editor (IDE), and view logs.
  • Queues: view and manage build queues.

Each group can be expanded to fine-tune the individual toggles, and each has Select all / Deselect all shortcuts.

How the layers combine

For a member to perform an action on a resource, both layers must allow it: the resource must be in their allowed list, and the matching permission toggle must be on. Admins and the owner skip both checks.

Related articles: Inviting workspace members and A member cannot see or use a resource.

If you get stuck, open a support ticket from the Tickets page or the chat widget.

Previous Inviting workspace members Next A member cannot see or use a resource

Still stuck? Open a ticket from the app or talk to an engineer.