Teammately Docs
Docs menu

concept

Workspaces and projects

Learn how Teammately organizes teams, projects, product goals, and access boundaries.

Workspaces and projects

Definition

The Workspace is the organization-level container. A Project is the operating boundary for one body of correctness work: its Project Agent Brief, Coverage Facets, Cases, Policies, Rubrics, Harnesses, Agent Setup, Project Settings, and Benchmarks.

Why it matters

The distinction matters because Workspace membership and Project participation are not interchangeable. A person can belong to the organization without having access to every Project, and a role label must not be treated as proof of a specific permission.

Where it appears in the product

Project Settings exposes General configuration, Regime, Input Schema, and Project Members. Organization-level administration belongs to the Admin Console. Benchmark work remains nested inside the selected Project and reuses that Project's governed objects.

Artifacts it affects

The boundary affects navigation, identifiers, membership, permissions, Project Agent Brief generations, Cases, governed standards, Harnesses, Benchmarks, Runs, and Contributions. Moving or copying artifacts between Projects is not implied by shared Workspace membership.

Boundary check

When a user cannot reach an object, confirm the Workspace, Project ID, Project membership, and object-specific assignment separately. When an artifact appears reusable across Projects, verify its source context, owner, and correctness boundary before recreating it. Shared organizational membership is never evidence that two Projects use the same Cases, standards, or Benchmark Versions.

Worked example

Same policy shape, different projects

One Workspace contains a billing-assistant Project and a security-assistant Project. The teams may use similar Rubric-writing practices, but their Project Agent Briefs, Cases, Policies, Harnesses, reviewers, and Benchmark evidence remain project-scoped. A user who can administer the billing Project is not assumed to have the same access in the security Project.

Related workflows

Concept / Project SettingsProject SettingsConfigure the project identity, evaluation Regime, case input contract, and project members.Reference / Project SettingsProject MembersGrant or remove user and group access to a project while keeping task assignment and artifact governance separate.Reference / Admin ConsoleAdmin ConsoleUnderstand the organization-level administration surfaces available at admin.teammately.ai.Troubleshooting / Recovery LibraryPermissions troubleshootingSeparate Project membership from Expert Contribution assignment and readiness when an expert has no tasks available.

Related reference pages

Reference / Reference LibraryIDs and keysUnderstand the identifiers used across Teammately projects, records, benchmarks, runs, policies, and rubrics.Reference / Reference LibraryPermissionsUnderstand the user-facing permission boundaries for projects, reviewers, settings, and expert UI access.Reference / Object ModelWorkspaces, projects, and target systemsModel organizational boundaries, product boundaries, and the AI system being governed.Reference / Agent SetupProject ContextMaintain the Project Agent Brief that gives Teammately agents stable, project-wide understanding.

Source confidence

Code-backed: Workspace and Project types establish the container boundary; Project Settings, Members, and Permissions expose the current project-scoped configuration and access surfaces. Organization-level behavior is intentionally left to the separately bounded Admin Console documentation.

Found something unclear?

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

Report a docs issue

Continue learning

Related docs

Learning Manual The Teammately correctness loop See how coverage, elicitation, case construction, evaluation, and improvement reinforce one another. Reference Library IDs and keys Understand the identifiers used across Teammately projects, records, benchmarks, runs, policies, and rubrics. Reference Library Permissions Understand the user-facing permission boundaries for projects, reviewers, settings, and expert UI access. Recovery Library Permissions troubleshooting Separate Project membership from Expert Contribution assignment and readiness when an expert has no tasks available.
AI context