{"query":"Reviewer and Project Access","corpusVersion":"local","generatedAt":"2026-09-13T04:40:38.646Z","results":[{"blockId":"governance.reviewer-project-access#reviewer-and-project-access","pageId":"governance.reviewer-project-access","title":"Reviewer and Project Access","pageTitle":"Reviewer and Project Access","url":"https://teammately.ai/docs/governance/reviewer-and-project-access.md","humanUrl":"https://teammately.ai/docs/governance/reviewer-and-project-access#reviewer-and-project-access","markdownUrl":"https://teammately.ai/docs/governance/reviewer-and-project-access.md","sectionId":"reviewer-and-project-access","kind":"reference","productArea":"governance","score":3162.126858024296,"reasons":["search_match","title_match","display_title_match","term_match","prefix_or_fuzzy_match"],"markdown":"# Reviewer and Project Access"},{"blockId":"project-settings.project-members#manage-access","pageId":"project-settings.project-members","title":"Manage access","pageTitle":"Project Members","url":"https://teammately.ai/docs/project-settings/project-members.md","humanUrl":"https://teammately.ai/docs/project-settings/project-members#manage-access","markdownUrl":"https://teammately.ai/docs/project-settings/project-members.md","sectionId":"manage-access","kind":"reference","productArea":"project_settings","score":1268.6140165011693,"reasons":["search_match","term_match"],"markdown":"## Manage access\n\n1. Open **Project Settings → Project Members**.\n2. Review existing principals and whether each grant belongs to a user or group.\n3. Add the smallest appropriate principal. Prefer a managed group when access follows a durable team responsibility.\n4. Before removing a grant, check active Contributions, reviews, and operational ownership that may need reassignment.\n5. Confirm the resulting member list and test the intended product path through ordinary authorization.\n\nGroup access follows the group relationship managed by the workspace; it should not be duplicated as many individual grants without an operational reason. A user can also have more than one access path, so removing one grant may not remove all effective access.\n\n> Access boundary\n>\n> Grant the smallest appropriate project scope. Do not copy credentials or sensitive material into project content as a substitute for access control.\n\nProject access does not grant secret values automatically. Harness secret grants remain explicit. Contribution selection also remains separate: an expert needs the applicable project access path and a scoped Contribution before completing assigned work.\n\nThis page makes no retention-period or post-removal visibility guarantee. Historical attribution and record access are governed by the records and permissions the current product exposes at the time they are inspected.\n\n{% related-card-grid title=\"Related governance\" %}\n- [Roles and permissions](/docs/governance/roles-and-permissions)\n- [Reviewer and project access](/docs/governance/reviewer-and-project-access)\n- [Request an Expert Contribution](/docs/expert-contributions/request-contribution)\n{% /related-card-grid %}"},{"blockId":"governance.reviewer-project-access#definition","pageId":"governance.reviewer-project-access","title":"Definition","pageTitle":"Reviewer and Project Access","url":"https://teammately.ai/docs/governance/reviewer-and-project-access.md","humanUrl":"https://teammately.ai/docs/governance/reviewer-and-project-access#definition","markdownUrl":"https://teammately.ai/docs/governance/reviewer-and-project-access.md","sectionId":"definition","kind":"reference","productArea":"governance","score":1046.7874122298322,"reasons":["search_match","page_title_match","term_match","prefix_or_fuzzy_match"],"markdown":"## Definition\n\nReviewer 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."},{"blockId":"governance.reviewer-project-access#related-objects","pageId":"governance.reviewer-project-access","title":"Related objects","pageTitle":"Reviewer and Project Access","url":"https://teammately.ai/docs/governance/reviewer-and-project-access.md","humanUrl":"https://teammately.ai/docs/governance/reviewer-and-project-access#related-objects","markdownUrl":"https://teammately.ai/docs/governance/reviewer-and-project-access.md","sectionId":"related-objects","kind":"reference","productArea":"governance","score":1043.740823378952,"reasons":["search_match","page_title_match","term_match","prefix_or_fuzzy_match"],"markdown":"## Related objects\n\nUse [Admin Console](/docs/admin-console) for organization roles and directory controls, [Project Members](/docs/project-settings/project-members) for project participation, and [Expert Contributions](/docs/expert-contributions) for assignment and expert-runtime state. Use the owning Policy, Rubric, Case, or Contribution page to determine approval.\n\n{% example-demo title=\"Qualified expert without project access\" %}\nA 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.\n{% /example-demo %}"},{"blockId":"governance.reviewer-project-access#fields-states-or-lifecycle-rules","pageId":"governance.reviewer-project-access","title":"Fields, states, or lifecycle rules","pageTitle":"Reviewer and Project Access","url":"https://teammately.ai/docs/governance/reviewer-and-project-access.md","humanUrl":"https://teammately.ai/docs/governance/reviewer-and-project-access#fields-states-or-lifecycle-rules","markdownUrl":"https://teammately.ai/docs/governance/reviewer-and-project-access.md","sectionId":"fields-states-or-lifecycle-rules","kind":"reference","productArea":"governance","score":1019.9407276004421,"reasons":["search_match","page_title_match","term_match","prefix_or_fuzzy_match"],"markdown":"## Fields, states, or lifecycle rules\n\n- A workspace or organization role does not automatically prove access to every Project.\n- Project membership does not automatically assign a person to every Expert Contribution.\n- Assignment makes work available to the intended expert; it does not pre-approve the expert's response.\n- Checkpoint and artifact approval state must be read from the Contribution or governed object itself.\n- Removing access can prevent future interaction without erasing already recorded attributable evidence.\n- API keys, service scopes, and customer integrations are separate authorization boundaries.\n- Exact permission keys and enforcement behavior should be read from current administration and project surfaces, not inferred from persona names."},{"blockId":"governance.reviewer-project-access#related-task-pages","pageId":"governance.reviewer-project-access","title":"Related task pages","pageTitle":"Reviewer and Project Access","url":"https://teammately.ai/docs/governance/reviewer-and-project-access.md","humanUrl":"https://teammately.ai/docs/governance/reviewer-and-project-access#related-task-pages","markdownUrl":"https://teammately.ai/docs/governance/reviewer-and-project-access.md","sectionId":"related-task-pages","kind":"reference","productArea":"governance","score":1007.0394657101473,"reasons":["search_match","page_title_match","term_match","prefix_or_fuzzy_match"],"markdown":"## Related task pages\n\n{% related-card-grid title=\"Related task pages\" %}\n- [Roles and Permissions](/docs/governance/roles-and-permissions)\n- [Reviewer Assignments and Statuses](/docs/expert-contributions)\n- [Permissions](/docs/reference/permissions)\n- [Product quickstart](/docs/quickstart)\n- [Task index](/docs/operating-manual/task-index)\n{% /related-card-grid %}"},{"blockId":"governance.reviewer-project-access#source-confidence","pageId":"governance.reviewer-project-access","title":"Source confidence","pageTitle":"Reviewer and Project Access","url":"https://teammately.ai/docs/governance/reviewer-and-project-access.md","humanUrl":"https://teammately.ai/docs/governance/reviewer-and-project-access#source-confidence","markdownUrl":"https://teammately.ai/docs/governance/reviewer-and-project-access.md","sectionId":"source-confidence","kind":"reference","productArea":"governance","score":995.4045259786224,"reasons":["search_match","page_title_match","term_match","prefix_or_fuzzy_match"],"markdown":"## Source confidence\n\nCode-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."},{"blockId":"concepts.workspaces-projects#workspaces-and-projects","pageId":"concepts.workspaces-projects","title":"Workspaces and projects","pageTitle":"Workspaces and projects","url":"https://teammately.ai/docs/concepts/workspaces-projects.md","humanUrl":"https://teammately.ai/docs/concepts/workspaces-projects#workspaces-and-projects","markdownUrl":"https://teammately.ai/docs/concepts/workspaces-projects.md","sectionId":"workspaces-and-projects","kind":"concept","productArea":"object_model","score":691.185551489945,"reasons":["search_match","term_match","prefix_or_fuzzy_match"],"markdown":"# Workspaces and projects"}]}