Docs

Role Management

Understand who can manage settings, who can work on delivery, and what each user type can see across company, customer, and project scopes.

role management guidewho can see what in Curoxiworkspace access control

How access works

Access in Curoxi is layered. A user can have a company-side role, a customer-side role, and project-level responsibilities. The final experience depends on that combination and on which modules are enabled for the workspace.

  • Company admins manage settings, licenses, billing controls, and company users
  • Company members focus on delivery work and assigned tasks
  • Customer users see only the modules enabled for their workspace
  • Project roles control actions such as GitHub setup, releases, and sprints

What to review first

  • Check whether the user is a company user or a customer user
  • Confirm the modules enabled for that workspace
  • Review project-level permissions before enabling delivery tooling

Best practice for access design

  • Give the smallest access needed for the role
  • Use company admin only for settings and account management
  • Review access whenever a user changes teams or customer responsibilities

What good role design improves

  • Less accidental configuration change
  • Cleaner customer visibility boundaries
  • Better auditability for who can do what

Explore Curoxi

Browse the core pages that explain how Curoxi works, how pricing is structured, and how to start a workspace.

Contact

Talk to sales or support

Route pricing questions, rollout discussions, and workspace setup needs to the right team.