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 Deleting a server

Projects & Git

Creating a project Connecting GitHub Project GitHub settings and webhook Connecting GitLab Branches and instances Tagging and filtering projects High availability with app nodes Project environments, extensions and deletion

Instances & Console

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

Agent Tasks

What agent tasks are Setting up agent tasks Running a task and reviewing the result Agent time and top-ups Agent insights and task filters

Monitoring & Backups

Monitoring your instance Backups and restore S3 storage, uploads and bulk backup actions Alert notifications (email and SMS)

Workspaces & Permissions

Inviting workspace members Member permissions and resource access A member cannot see or use a resource Audit log and server activity

Account & Security

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

Billing & Plans

Plans and pricing Upgrading and managing your subscription If a project subscription goes unpaid The channel partner program Onboarding a client as a partner

Support & Tickets

Opening a support ticket Getting help from the CICDoo team

Troubleshooting

Troubleshooting: cannot connect a server Troubleshooting: a deployment failed Troubleshooting: git push fails with 403 after moving a repository 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, using the Member Permissions wizard.

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, on the Workspaces tab, by clicking the shield icon (Manage permissions) next to the member. This opens the Member Permissions wizard. Changes save on their own; wait for "All changes saved" in the footer.

  1. Check that they are a member of the workspace.
    • Look in the Members card on the Workspaces tab. If they are not listed, invite them first. See Inviting workspace members.
    • If their row has an Invited badge, they have not signed up yet. Their permissions apply only once they create an account with that email address.
  2. Check their role on the Role step.
    • An Admin bypasses every check, so if someone should have full access, setting their role to Admin fixes everything at once.
    • A Member starts with no access, so anything not granted in the wizard is denied.
  3. Check the workspace-wide switches on the Role step.
    • Servers page missing: switch on View servers. Adding, editing, deploying or deleting servers each need their own switch underneath it.
    • Projects page or console missing: switch on View projects & console. While it is off, nothing granted on the Projects step takes effect.
    • Dashboard missing (they land on Projects instead): switch on View the workspace dashboard.
    • Queue or Audit Log missing from the menu: switch on View the job queue or View the audit log.
    • Cannot see billing or invoices: switch on the matching option under Billing.
  4. Check what they can reach.
    • If Access all workspace resources is on, they can reach everything, so skip to step 5.
    • Otherwise, on the Servers step, tick each server they need.
    • On the Instances step, make sure each instance they need is switched on. An instance the member cannot reach stays out of the console even when its project is granted. Use Filter by project to bring a project's instances into the list.
  5. Check the project's level on the Projects step.
    • A project set to No access grants nothing. New projects always start at No access for existing members.
    • Visible only shows the project but allows no actions.
    • Read only gives Logs and Monitoring only. Operate only adds Restart, Stop, Backups and Merge, but not the IDE, settings or SSH.
    • Click the project name to see the individual switches and turn on exactly what is missing.
  6. Match the blocked action to its switch.
    • Cannot open project settings: Project settings.
    • Cannot restart or upgrade an instance: Restart. Cannot stop it: Stop.
    • Cannot create backups: Backups. Cannot merge branches: Merge.
    • Cannot add or remove instances: Create instances or Remove instances.
    • Cannot use the web editor: IDE. Cannot change instance settings: Instance settings.
    • Cannot sign in to Odoo as a user: Connect as user.
    • Cannot open SSH or database access: SSH & database. This is separate from Connect as user, and the member also needs to have registered their own SSH key. See SSH access to instances.
    • Can see logs but not monitoring charts, or the other way round: Logs and Monitoring are separate switches.
    • Cannot see or approve agent tasks: Agent tasks, and Approve plans (which needs Agent tasks on).
  7. Check for an instance override on the Instances step.
    • An instance set to Custom no longer follows its project, so a permission you just added to the project will not reach it. Switch on Only show overrides to find these, then either fix the switches or set the instance back to Same as project.
  8. Check for a permission template.
    • If the project row follows a workspace template, its switches come from the template. Edit the template in the Permission Templates card, or pick a different level for that row.
  9. Ask the member to reload the app and try again.

Still not working?

If the member is in the workspace, can reach the resource, holds the right switch, and the action still fails, note the exact action and the error message they see (for example "You do not have permission to access this section."). The Audit Log records denied actions with an Outcome of Denied, which shows exactly what was refused and when. See Audit log and server activity.

Related: Member permissions and resource access, Inviting workspace members.

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

Previous Member permissions and resource access Next Audit log and server activity

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