Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.samelogic.com/llms.txt

Use this file to discover all available pages before exploring further.

Access control in Samelogic is organized around workspaces and projects so teams can share context without oversharing sensitive data.

​
Access model

  • Workspace: top-level container for teams and billing
  • Projects: scoped environments for captures, elements, and replays
  • Elements and replays: inherit access from the project

​
Typical roles

Many teams use a simple role model:
  • Owner/Admin: manage billing, users, and security settings
  • Member: capture and manage elements and replays
  • Viewer: read-only access for stakeholders
Exact roles and permissions may vary by plan. Use the least-privilege model that still lets teams collaborate.

​
Best practices

  • Review access quarterly or per release.
  • Restrict production capture to approved users.
  • Use project boundaries to separate teams or environments.