Skip to main content

​
Team and Access

Chatobserver separates day-to-day usage from administrative control. Team and access settings determine who can enter a workspace and what level of authority they have.

​
Common responsibilities in this area

  • inviting teammates
  • removing access
  • reviewing current members
  • assigning roles
  • managing API access

​
Roles

Current workspace role labels include:
  • owner
  • admin
  • member
Use the lightest role that still lets someone do their job. Reserve owner-level access for the people who actually need to control the account.

​
Invitations and workspace access

Invitations are the cleanest way to onboard new people into the right workspace context from the start. Before you send them, confirm:
  • the email address is correct
  • the role is appropriate
  • the correct workspace access is selected
Access mistakes are easier to prevent than to unwind later.

​
API access

API keys are managed from the dashboard and are scoped to the workspace that created them. Treat them like production secrets:
  • store them in a secret manager
  • do not paste them into shared docs
  • rotate or revoke keys when ownership changes
The full token is shown once at creation time, so plan handoff accordingly.

​
Operational guidance

Review access whenever:
  • a teammate changes role
  • a contractor leaves
  • ownership of reporting or automation changes
  • a workspace is repurposed for a new team
Access management is part of data hygiene, not a one-time setup task.