Teammately Docs
Docs menu

reference

Reviewer and Project Access

Route reviewers and project participants to the work they are qualified to inspect or approve.

Reviewer and Project Access

Definition

Reviewer access combines several explicit boundaries. Organization roles are managed in the Admin Console. Project membership determines access to a particular project. Expert Contribution assignment determines which scoped work an expert receives. Artifact approval authority belongs to the owning workflow and must not be inferred from a general role label.

Fields, states, or lifecycle rules

  • A workspace or organization role does not automatically prove access to every Project.
  • Project membership does not automatically assign a person to every Expert Contribution.
  • Assignment makes work available to the intended expert; it does not pre-approve the expert's response.
  • Checkpoint and artifact approval state must be read from the Contribution or governed object itself.
  • Removing access can prevent future interaction without erasing already recorded attributable evidence.
  • API keys, service scopes, and customer integrations are separate authorization boundaries.
  • Exact permission keys and enforcement behavior should be read from current administration and project surfaces, not inferred from persona names.

Use Admin Console for organization roles and directory controls, Project Members for project participation, and Expert Contributions for assignment and expert-runtime state. Use the owning Policy, Rubric, Case, or Contribution page to determine approval.

Worked example

Qualified expert without project access

A specialist is the right reviewer for a source-authority Contribution but cannot open the assigned task. The operator checks organization membership, then Project membership, then Contribution assignment. Granting the missing Project access makes the task reachable; the assignment still controls which work is presented, and the specialist's later Checkpoint decision remains a separate recorded action.

Source confidence

Code-backed: Project Permissions, Project Members, user, and workspace types establish project participation and role presentation. Contribution pages define assignment, runtime, and approval state separately; this page does not claim a complete authorization matrix.

Related task pages

Reference / Governance and ReproducibilityRoles and PermissionsUse roles and permissions to route ownership, review, and approval work clearly.Concept / Expert ContributionsExpert ContributionsCoordinate benchmark-scoped expert work, attributable judgment, governed artifacts, and the decisions that move correctness forward.Reference / Reference LibraryPermissionsUnderstand the user-facing permission boundaries for projects, reviewers, settings, and expert UI access.Quickstart / Learning ManualProduct quickstartConfigure one project foundation, one benchmark slice, one expert contribution, one evaluation, and one evidence-backed improvement.Concept / Operating ManualTask indexRoute correctness work to the current project foundation, benchmark workspace, evaluation, or improvement surface.

Found something unclear?

Report outdated, unsupported, or confusing docs so we can fix the source page.

Report a docs issue

Continue learning

Related docs

Governance and Reproducibility Roles and Permissions Use roles and permissions to route ownership, review, and approval work clearly. Expert Contributions Expert Contributions Coordinate benchmark-scoped expert work, attributable judgment, governed artifacts, and the decisions that move correctness forward. Reference Library Permissions Understand the user-facing permission boundaries for projects, reviewers, settings, and expert UI access.
AI context