---
id: orientation.product-map
title: Product map
summary: Navigate Teammately across workspace entry points, project foundations, benchmark workspaces, expert contribution UI, and administration.
kind: concept
product_area: introduction
status: stable
updated: 2026-09-07
canonical: /docs/getting-oriented/product-map
---

# Product map

Teammately separates reusable project foundations from benchmark-scoped work. The Main UI uses the selected project and benchmark to route operators to the right scope. Experts receive a focused Expert contribution UI. Admin Console owns organization-level controls, while AI-assisted background work prepares and coordinates bounded tasks.

> Surface routing
>
> Before changing an artifact, identify its scope. Project foundations can affect several benchmarks; dataset selection, Contributions, Evaluations, and Improvement Sessions belong to a selected benchmark or benchmark version.

## Definition

The **Main UI** begins at Project Home and groups project-level work into Correctness Governance, Coverage Facets, Assets, Agent Setup, and Project Settings. After a benchmark is selected, its workspace exposes Benchmark Overview, Benchmark Datasets, Coverage Management, Expert Contributions, Benchmark Evaluations, and Improve.

The **Expert contribution UI** presents one Contribution and its form, chat, interview, case-review, checkpoint, waiting, and completion states. The expert does not need the full project navigation to supply attributable judgment.

The **Admin Console** contains organization administration such as members, groups, roles, domain controls, integrations, and other code-backed administrative surfaces. Public docs keep detailed security, billing, retention, and compliance claims outside the boundary unless separately verified.

**AI-assisted background work** can index reference material, prepare contributions, suggest coverage or standards, construct cases, run evaluations, and coordinate candidate exploration. Its outputs retain the authority of the owning artifact and workflow.

## Decision checkpoint

| Work | Scope | Surface |
| --- | --- | --- |
| Project purpose and knowledge | Project | Agent Setup |
| Policies and rubrics | Project | Correctness Governance |
| Dimensions, Topics, and construction patterns | Project | Coverage Facets |
| Reusable Cases and Harnesses | Project | Assets |
| Input architecture | Project | Project Settings |
| Benchmark-level run fields | Benchmark | Benchmark Evaluations |
| Selected Cases, representation, and snapshots | Benchmark | Benchmark Datasets |
| Coverage setup, Stories, Case Review, and Foundry | Benchmark | Coverage Management |
| Specialist requests and contributed artifacts | Benchmark | Expert Contributions |
| Runs, results, Compare, and Arena | Benchmark version | Benchmark Evaluations |
| Goal Contracts, candidates, and frontier | Benchmark version | Improve |

## How selection affects navigation

Project surfaces require a project. Benchmark surfaces also require a benchmark, and Evaluations or Improve may resolve the current benchmark version. If a destination is unavailable, confirm the current selectors before assuming that the feature or data is missing.

Project folders and search help users move across a larger workspace, but they do not change artifact ownership. Search results and creation actions should preserve the selected project or benchmark scope.

{% surface-map title="Teammately product surfaces" %}
{% /surface-map %}

{% example-demo title="Route a new rubric need" %}
An evaluation exposes inconsistent handling of expired agreements. The operator uses the benchmark workspace to request an Expert Contribution with the failed cases. The expert works in the focused contribution UI. The resulting rubric is reconciled in Correctness Governance at project scope, then included in a later benchmark version and evaluation.
{% /example-demo %}

## Related workflows

{% related-card-grid title="Related workflows" %}
- [Task index](/docs/operating-manual/task-index)
- [Operating Teammately end to end](/docs/getting-oriented/operating-teammately-end-to-end)
- [Product quickstart](/docs/quickstart)
{% /related-card-grid %}

## Related reference pages

{% related-card-grid title="Related reference pages" %}
- [Key objects and relationships](/docs/getting-oriented/key-objects-and-relationships)
- [User roles](/docs/getting-oriented/user-roles)
- [Product boundaries](/docs/introduction/product-boundaries)
{% /related-card-grid %}

## Source confidence

Code-backed: current navigation and active project, benchmark, Contribution, and administration routes establish the scope and labels described here.