Skip to content
Codeskop

Roles and lenses

Everyone on the team sees the same issues, data and pages. A member's lens orders the menu for their work and decides which actions they can take.

Roles

  • Owner and Admin: everything, including the team, billing, API keys, alert rules, notification channels and SDK settings. They always use the All tools lens.
  • Member: sees everything. What they can do depends on their lens.

Lenses

  • Engineering: developers and engineering leads.
  • Product & QA: product managers and QA / test.
  • Support & CX: support and customer success.
What each lens can do
ActionEngineeringProduct & QASupport & CX
Connect or change integrations (task managers, GitHub, GitLab)YesYesNo
Create ticketsYesYesYes
Fix with AIYesNoNo
Assign issues and change their statusYesYesNo
Comment and @mentionYesYesYes

Who sets a member's lens

An owner or admin, in Settings → Team or when inviting someone. Until one is set, the lens follows what the person said they do: Developer and Engineering lead get Engineering, Product and QA / Test get Product & QA, and Support gets Support & CX.

Looking through another lens

Anyone can switch lens from the top of the sidebar to see the menu another team uses. It only changes the menu: what you can do always follows your own lens.

Plans still apply

A lens never unlocks a feature your plan doesn't include. Tickets and Fix with AI need the Growth plan or above, whatever the lens.