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

A member cannot see or use a resource

A checklist for fixing a workspace member who cannot see or act on a project, instance, or server.

Quick checklist

When a teammate reports that a project, instance, or server is missing for them, or that an action is blocked, work through this list. All fixes are made by the workspace owner (or an admin) in Settings, Workspaces tab, using the shield icon next to the member's name, which opens the Member Permissions modal.

  1. Are they actually a member of the workspace? Check the Members card on the Workspaces tab. If they are not listed, invite them by email first. See Inviting workspace members.

  2. Is the resource in their allowed lists? In the permissions modal, expand Resource Access. There are separate lists for Projects, Instances, and Servers, each with a search box. If the resource is not ticked, the member cannot access it. An empty list means no access to that resource type at all, so a freshly restricted member with nothing ticked will see nothing.

  3. Do they have the relevant permission toggle? Resource access alone is not enough. The matching feature toggle must also be on. For example: - They can see a project but cannot open its settings: check "Edit project settings" under Projects and Console. - They cannot restart an instance: check "Restart / Upgrade" under Instances / Console. - They cannot view logs, use the editor, create backups, merge branches, stop or remove instances, or connect as a user: each of these has its own toggle under Instances / Console. - They cannot add, deploy, edit, or delete servers: check the Servers group. - They cannot see build queues: check the Queues toggle.

  4. Is their role set correctly? In the same modal, the Role selector offers Member and Admin. Admins bypass all permission and resource access checks, so if someone should have full access, setting their role to Admin resolves everything at once. The workspace owner always has full access and never needs configuring.

  5. Save and re-test. Click Save Permissions, then ask the member to reload the app and try again.

Still not working?

If the member is in the workspace, the resource is ticked, the toggle is on, and it still fails, note the exact action and error message. For a full explanation of how the layers combine, see Member permissions and resource access.

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

Previous Member permissions and resource access

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