Skip to content

Team and Access

Good agent operations are rarely a solo job.

Even a small rollout usually involves at least three kinds of people:

  • someone who owns the workspace and release decisions
  • someone who operates the agent day to day
  • someone who reviews answers from an expert or stakeholder point of view

Organization users page for managing who can join the team

Two layers of team access

Collaboration in Codeer happens at two scopes:

  • Organization: who belongs to the broader team
  • Workspace: who can operate a specific agent, channel, and history set

That means adding a teammate is usually a two-step process:

  1. add them to the organization
  2. give them access to the right workspace

A practical rollout pattern

For Consultation Desk, a common setup looks like this:

  • owner: the person responsible for release and access control
  • admin: the operator who edits, tests, publishes, and reviews histories
  • member: an expert reviewer or collaborator who needs access without owning the whole system

In this section