# Project Settings Generated: 2026-11-11T09:05:00.745Z Source build: local Canonical docs: https://teammately.ai/docs --- id: project-settings.overview title: Project Settings summary: Maintain project understanding, Lemon instructions, Regime, input schema, members, and secret grants in the current settings surface. kind: concept product_area: project_settings status: stable updated: 2026-10-30 canonical: /docs/project-settings --- # Project Settings Project Settings maintains the current configuration shared by a project's Benchmark work. Open the relevant tab for the object you intend to change. ## Definition The settings surface contains **General**, **Project Context**, **Reference Materials**, **Lemon instructions**, **Regime**, **Input Schema**, **Project Members** and **Secrets**. | Setting | Owns | Important distinction | | --- | --- | --- | | General | Project name and Project Memo | Memo is human-facing text, not agent context | | Project Context | Project Agent Brief | Stable project understanding | | Reference Materials | Sources and indexed content | Source refresh does not rewrite the brief | | Lemon instructions | Configured activity guidance | Project override and automatic history | | Regime | Framework, points, gates and guidance | Settings do not approve individual artifacts | | Input Schema | Canonical input and materials | Benchmark planning inherits this contract | | Project Members | Individual workspace users' Project access | Membership is separate from task assignment | | Secrets | Project secret access and grants | Values are not Run metadata or source code | ## Change boundaries A project setting can affect future work across multiple Benchmarks. Accepted tasks and Runs retain the inputs, settings and instructions they captured. Saving current settings does not rewrite historical results. Changes record their actor, scope, time and before/after content automatically where the owning setting provides history. Users do not create or publish a separate settings version to make an edit take effect. ## Operating sequence Inspect the current value and its scope. Make the intended edit, save through the owning control and read its authoritative result. Resolve a concurrent-change response without discarding another operator's work. Use Input Schema to change required Case materials. Use Regime to configure point interpretation. Use Lemon instructions for activity guidance and the Project Agent Brief for stable product meaning. ## Related work Benchmark Datasets owns selected membership and Snapshots. Coverage Design owns input requirements and adoption decisions. Expert Contributions owns a request, its accepted plan and attributable judgments. Run details preserve recorded execution metadata. They do not create a current Run Metadata settings tab. ## Related reference pages {% related-card-grid title="Related reference pages" %} - [General Project Settings](/docs/project-settings/general) - [Project Context](/docs/agent-setup/project-context) - [Reference Materials](/docs/agent-setup/reference-materials) - [Lemon Instructions](/docs/project-settings/lemon-instructions) - [Regime Settings](/docs/project-settings/regime) - [Project Input Schema](/docs/project-settings/input-schema) - [Project Members](/docs/project-settings/project-members) - [Project Secrets](/docs/project-settings/secrets) {% /related-card-grid %} --- id: project-settings.general title: General Project Settings summary: Maintain the project name and Project Memo for your teammates. kind: reference product_area: project_settings status: stable updated: 2026-11-06 canonical: /docs/project-settings/general --- # General Project Settings ## Definition General settings contain the project **Name** and **Project Memo**. The name identifies the project in Teammately. The memo is project-level descriptive metadata for people working in the project. > Project Memo is not agent context > > The Project Memo is not injected into prompts and does not replace Project Context, Reference Materials, Lemon instructions, or Review Screens. Use the corresponding Project Settings tabs for project understanding and Lemon guidance. Use the memo for a concise human-readable purpose, ownership note, or operating reminder. Avoid secrets and avoid relying on it for behavior that must be reproducible in a Harness or evaluation. ## Fields, states, or lifecycle rules - Name is the editable project identifier shown to people. - Project Memo is human-facing descriptive text and has no prompt-injection state. - Saving either field changes current project metadata without versioning historical benchmark results. ## Choose the right surface | Information | Put it in | Reason | | --- | --- | --- | | Human-facing project purpose or ownership note | Project Memo | Describes the project without affecting behavior | | Domain and operating context for agents | Project Context | Enters the governed agent-facing setup | | Expected candidate behavior | Policies and Rubrics | Defines the standard and its applicability | | Guidance for Teammately's configured activities | Lemon instructions | Guides preparation, elicitation, and rubric evaluation | | Source documents and connected knowledge | Reference Materials | Preserves source identity and indexing state | | Candidate implementation or prompt logic | Harness | Gives the executable candidate an exact Version | | Experiment-only descriptors | Run Metadata | Keeps context attached to the relevant Run | Changing the project name updates how people locate the project; it does not create a new Benchmark Version. Changing the memo likewise does not invalidate a Dataset Snapshot or alter historical Runs. If a memo change represents a real change in benchmark purpose, update the governed coverage, evaluator, and versioned records surfaces separately. {% example-demo title="Example: memo versus context" %} The memo says that the project is owned by the support automation team and covers policy-grounded replies. Project Context explains the product domain and operating constraints to Teammately agents. Policies and Rubrics define the grounding requirement and its applicability. Lemon instructions guide Teammately's configured activities; the candidate Harness implements the evaluated system's grounding behavior. {% /example-demo %} {% related-card-grid title="Agent-facing configuration" %} - [Policies and Rubrics](/docs/correctness-governance/policies-and-rubrics) - [Project Context](/docs/agent-setup/project-context) - [Lemon Instructions](/docs/project-settings/lemon-instructions) - [Harnesses](/docs/assets/harnesses) {% /related-card-grid %} ## Related task pages {% related-card-grid title="Related task pages" %} - [Project Context](/docs/agent-setup/project-context) - [Lemon Instructions](/docs/project-settings/lemon-instructions) {% /related-card-grid %} --- id: project-settings.input-schema title: Project Input Schema summary: Define the canonical input architecture, case-material fields, and accepted artifact formats for project cases. kind: reference product_area: project_settings status: stable updated: 2026-10-30 canonical: /docs/project-settings/input-schema --- # Project Input Schema ## Definition Project Input Schema is the project-managed contract for future cases. It declares the primary input architecture, optional structured-input schema, named case-material fields, and artifact families or file extensions the project accepts. The active architectures are **plain text**, **chat**, and **structured**. The schema is a project singleton rather than a versioned benchmark object. When no setting exists, the default accepts one plain-text user message and no case materials or artifacts. ## Fields, states, or lifecycle rules - `architecture` is `plain_text`, `chat`, or `structured`. - Structured architecture requires a bounded `structuredInputSchema`. - `caseMaterialSchema` is a closed, flat object. Each material key has a label, optional description, required flag, type, and any accepted artifact rules. - Material keys use lowercase letters, digits, and underscores, start with a letter, and remain flat. - `acceptedArtifacts` declares project-level artifact families. Supported families are image, document, tabular, presentation, source text, and audio. - A case-material artifact rule must be a subset of the artifact families admitted at the project root. - Saving a new schema governs future case validation. Operators should inspect existing cases before making a change that would make current content invalid. ## Canonical case content The primary case payload is `content.input`. Optional supporting values and artifacts live in `content.case_materials`. The product renders `record_content.case_view` so people and execution adapters can inspect the canonical content consistently; that view is a projection rather than an alternate authoring contract. Static support passed to a Harness uses `case_material_refs`. An executable or queryable environment uses an optional `world_instance_ref`. Do not collapse static documents, images, or values into the world boundary merely because a candidate consumes them during a Run. {% example-demo title="Example: structured support case" %} A project selects structured input with `question` and `customer_tier` properties. It declares a required `policy_document` case material that accepts PDF documents and an optional `account_history` tabular material. A case is valid only when its structured input matches the schema and the required document is present in the accepted format. {% /example-demo %} ## Related task pages {% related-card-grid title="Related task pages" %} - [Project Settings](/docs/project-settings) - [Product Quickstart](/docs/quickstart) - [Cases](/docs/assets/cases) - [Review Screens](/docs/assets/review-screens) {% /related-card-grid %} --- id: agent-setup.behavior-instruction title: Lemon Instructions summary: Edit current Markdown guidance for configured Lemon activities with project inheritance and automatic change history. kind: reference product_area: project_settings status: stable updated: 2026-10-30 canonical: /docs/project-settings/lemon-instructions --- # Lemon Instructions ## Definition Lemon instructions let authorized administrators and project managers maintain guidance for the configured activities that prepare, conduct and evaluate correctness work. Open **Admin → Organization Settings → Lemon instructions** for workspace guidance or **Project Settings → Lemon instructions** for a project override. A saved project instruction takes precedence over workspace guidance, then the reviewed default. ## Fields, states, or lifecycle rules Each configured activity has one Markdown document: - Review expert feedback. - Draft policies. - Draft case-specific checks. - Plan expert interviews. - Summarize expert interviews. - Plan expert contributions. - Adjust contribution follow-ups. - Create review alternatives. - Identify coverage observations. - Evaluate against rubrics. The catalog defines the configurable scope. Editing guidance does not change fixed tool authority, output contracts, binary evaluation semantics or human approval requirements. ## Save or reset Choose an activity, edit its current guidance and Save. Reset restores inheritance while retaining change history. A concurrent edit is reported instead of silently overwriting newer content. History records who changed the document, when, its scope and its before/after content automatically. Users do not create, name, publish or promote a prompt version. Accepted work captures the effective instructions it uses. A later edit changes future work; it does not rewrite earlier accepted inputs, completed Contributions or existing results. ## Write useful guidance State the desired outcome, relevant context and concrete boundaries. Keep one-time Benchmark questions in the Contribution or Goal rather than permanent project guidance. Allow the agent to interpret the request and select useful tools within its authority. Do not encode every conversation as a fixed classification or mandatory sequence. Review how guidance interacts with the Project Agent Brief, source materials and current standards. A well-written instruction supports reasoning; it cannot turn an unapproved suggestion into a Policy or an absent judgment into a score. ## Related task pages {% related-card-grid title="Related task pages" %} - [Agent Setup](/docs/agent-setup) - [Project Context](/docs/agent-setup/project-context) - [Correctness Governance](/docs/correctness-governance) - [Project Settings](/docs/project-settings) {% /related-card-grid %} --- id: project-settings.project-members title: Project Members summary: Manage direct Project memberships and understand group-based access while keeping task assignment and artifact governance separate. kind: reference product_area: project_settings status: stable updated: 2026-11-06 canonical: /docs/project-settings/project-members --- # Project Members ## Definition Use **Project Settings → Project Members** to add or remove direct user memberships. Project permissions can be assigned to individual users or workspace groups, so a person's effective access can also depend on their group membership and workspace role. Membership is not the same as selecting an expert for a Contribution, assigning a review task, or approving an artifact. Those workflows add scoped responsibility inside an already accessible project. Before removing access, review the person's active Contributions and arrange follow-up with the responsible owner. Confirm the resulting access through direct Project grants, workspace-group permissions, and workspace roles. ## Fields, states, or lifecycle rules - Each direct membership names an individual workspace user. - Adding a grant creates a project access path. - Removing a grant removes that current Project access path. - Effective access can remain through a workspace-group permission or workspace role after a direct membership is removed. ## Manage access 1. Open **Project Settings → Project Members**. 2. Review the listed users and their workspace status and organization role. 3. Choose **Add Members**, select the workspace users who need access, and add them. 4. Before removing a grant, coordinate any continuing Contribution, review, or operational work with its responsible owner. 5. Confirm the resulting member list and test the intended product path through ordinary authorization. Workspace role assignments are managed in **Admin → Directory → Members**. Removing direct Project membership does not change the person's workspace role, remove group-based permissions, or erase recorded Contributions and decisions. Check effective access after a membership change. > Access boundary > > Grant the smallest appropriate project scope. Do not copy credentials or sensitive material into project content as a substitute for access control. Project 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. Recorded responses and decisions keep their attribution. Access to those records follows the applicable workspace, Project, and workflow permissions. {% related-card-grid title="Related governance" %} - [Roles and Permissions](/docs/governance/roles-and-permissions) - [Reviewer and Project Access](/docs/governance/reviewer-and-project-access) - [Request an Expert Contribution](/docs/expert-contributions/request-contribution) {% /related-card-grid %} ## Related task pages {% related-card-grid title="Related task pages" %} - [Request an Expert Contribution](/docs/expert-contributions/request-contribution) - [Complete an Expert Contribution](/docs/expert-contributions/complete-contribution) {% /related-card-grid %} --- id: project-settings.regime title: Regime Settings summary: Configure scoring frameworks, point ranges, increments, and guidance with one current-settings save. kind: reference product_area: project_settings status: stable updated: 2026-10-30 canonical: /docs/project-settings/regime --- # Regime Settings ## Definition Open **Project Settings → Regime** to configure how applicable rubric judgments contribute to Case and benchmark results. The framework, point ranges, increments and guidance form one current configuration. ## Fields, states, or lifecycle rules - Positive and penalty limits can be edited independently. - Point increments are positive decimals; the editor offers common increments and custom entry. - Zero is permitted where the configured treatment allows it. - Gate and point guidance explain assignment expectations. - One Save applies the configuration and guidance together. - A concurrent change is reported instead of silently overwritten. New numerical configurations start with a signed point range from -5 to +10. There is no configurable minimum magnitude. Existing rubric assignments must remain compatible with the chosen ranges and step. ## Save current settings Review the framework and ranges together with the current assignments. Save after checking whether the values still express the intended consequence of each rubric. A failed save preserves the editor draft. Resolve the reported conflict or invalid configuration and save the intended current values. Saving settings does not itself approve a Rubric, replace an assignment rationale or confirm expert review. ## Point interpretation Current point scores preserve negative values and have no per-Case floor or cap. A gated framework also distinguishes mandatory-gate eligibility from the point calculation. Missing judgments remain incomplete. Read the score guide before interpreting a large penalty or a zero score. A zero caused by a completed gate failure has a different meaning from an unscored Case with no applicable points. ## Historical work Saving current settings preserves existing assignments and their attribution. Accepted Benchmark Versions, evaluation tasks and results retain the configuration they captured. Changes are recorded automatically with their actor, time, scope and before/after content. Users do not create, select, publish or promote a separate configuration version to make the change take effect. ## Related task pages {% related-card-grid title="Related task pages" %} - [Rubric Points and Benchmark Scores](/docs/correctness-governance/scoring) - [Policies and Rubrics](/docs/correctness-governance/policies-and-rubrics) - [Run a Benchmark Evaluation](/docs/benchmark-evaluations/run-evaluation) {% /related-card-grid %} --- id: project-settings.secrets title: Project Secrets summary: Grant project Harnesses access to workspace credentials through scoped secret permissions. kind: reference product_area: project_settings status: stable updated: 2026-11-06 canonical: /docs/project-settings/secrets --- # Project Secrets ## Definition Open **Project Settings → Secrets** to manage the project's access to supported workspace secrets. Grant the intended credentials through the owning Harness controls instead of copying values into candidate source. ## Fields, states, or lifecycle rules - Secret identity and access metadata are different from the secret value. - Project access and an individual Harness grant have different scopes. - Rotation changes the secret through its owning workspace operation. - Archiving or removing access can affect future credential resolution. - Existing Runs retain their recorded candidate and execution identities. ## Grant deliberately Identify the service the candidate needs and the exact Harness that should use it. Review project and Harness access rather than assuming that workspace membership grants every candidate the same credentials. Keep values out of the Project Agent Brief, Cases, Reference Materials, copied agent tasks, Run labels and metadata. A model or provider name is descriptive configuration, not a credential grant. ## Review changes Use the current secret and grant controls for creation, rotation, access and archive operations. Read reported failures before retrying a logical change. A display row or masked value does not establish that a candidate can resolve the secret during execution. When debugging, inspect the Run's configuration and authorized grant metadata. Do not paste secret values into a conversation to prove that a credential exists. ## Related task pages {% related-card-grid title="Related task pages" %} - [Project Settings](/docs/project-settings) - [Harnesses](/docs/assets/harnesses) - [Evaluation Execution Settings](/docs/benchmark-evaluations/execution-settings) {% /related-card-grid %} --- id: agent-setup.project-context title: Project Context summary: Maintain the Project Agent Brief that gives Teammately agents stable, project-wide understanding. kind: reference product_area: agent_setup status: stable updated: 2026-11-06 canonical: /docs/agent-setup/project-context --- # Project Context ## Definition Open **Project Settings → Project Context** to edit the **Project Agent Brief**. The brief gives Teammately agents stable project-wide understanding: what the specialist AI is for, which behavior matters, important constraints, terminology, and other context that should carry across coverage, contribution preparation, case construction, and improvement work. The Project Agent Brief is different from the Project Memo in General settings. The memo is administrative project text and explicitly is not used as prompt or agent context. Put agent-relevant project understanding in Project Context. ## Fields, states, or lifecycle rules - The brief is scoped to the project and reused across benchmark workspaces. - Editing the brief changes future agent context; it does not rewrite completed Contributions, Runs, or Lemon Goal Session history. - The brief provides orientation and constraints, not governed correctness authority. Policies and rubrics remain in Correctness Governance. - Controlling source material belongs in Reference Materials. Summarize stable project intent in the brief and keep source-backed detail in the indexed material. - The brief should state product-specific meaning directly. Avoid copying transient benchmark goals, one expert's unconfirmed opinion, or a temporary candidate hypothesis into permanent project context. ## Writing a useful brief Describe the specialist AI's purpose, users, important domain vocabulary, expected interaction shape, and constraints that affect many workflows. Include explicit boundaries where agents might otherwise make unsafe assumptions. Name controlling authorities without duplicating entire manuals. Review the brief when the product purpose, domain, input architecture, or correctness boundary changes materially. If only one benchmark needs a special objective, put it in that benchmark's setup or Contribution. If only one Lemon Goal Session needs a constraint, put it in the Goal. {% example-demo title="Example: project context boundary" %} The brief states that a procurement assistant supports internal buyers, must distinguish current agreements from expired ones, and should expose uncertainty rather than invent an exception. The current agreements themselves remain indexed Reference Materials. The exact evaluation target for expired-agreement cases belongs to the benchmark and Lemon Goal Session, not the brief. {% /example-demo %} ## Related task pages {% related-card-grid title="Related task pages" %} - [Product Quickstart](/docs/quickstart) - [Reference Materials](/docs/agent-setup/reference-materials) - [Request an Expert Contribution](/docs/expert-contributions/request-contribution) {% /related-card-grid %} --- id: agent-setup.reference-materials title: Reference Materials summary: Connect project knowledge, inspect indexing state, and verify the blocks available to Teammately agents. kind: reference product_area: agent_setup status: stable updated: 2026-11-06 canonical: /docs/agent-setup/reference-materials --- # Reference Materials ## Definition Open **Project Settings → Reference Materials** to manage project knowledge that Teammately agents may use. **Materials** manages sources such as websites, Git repositories, and uploaded files. **Indexed Reference** shows the published reference blocks available after extraction and indexing. Reference Materials is project understanding, not governed correctness. A manual can support an agent's reasoning or an expert Contribution without automatically becoming a policy, rubric, case, or approved statement. ## Fields, states, or lifecycle rules - A Connection identifies a source and its ingestion or freshness state. - Website, Git, and file connections follow source-specific discovery and processing paths. - Indexed Reference presents published blocks rather than a second editable copy of the source. - Publication is atomic: agents should see a coherent published generation rather than a partially updated index. - Reconnecting, refreshing, or processing a source can create a newer indexed generation. Completed Runs and Contributions keep their own recorded snapshot boundaries. - Removing a Connection or source does not imply that previously materialized policies, rubrics, cases, or contribution records should be silently deleted. - File upload acceptance depends on file type, size, content verification, and the active source-processing path. ## Materials and Indexed Reference Use Materials to answer: which sources are connected, when were they processed, and does a source need attention? Use Indexed Reference to answer: what text or blocks can agents actually retrieve now? A successful connection is not enough if the expected controlling material never appears in Indexed Reference. When sources conflict, retain the conflict in the indexed material and resolve correctness through an expert contribution or governed policy. Do not rewrite Project Context to hide source disagreement. {% example-demo title="Example: reference publication check" %} A team connects a policy website and a Git repository containing operational rules. After processing, the operator opens Indexed Reference and searches for the current exception clause. The website block is current, while the repository still contains an older rule. The operator keeps both sources visible and requests an expert Contribution to establish the controlling policy. {% /example-demo %} ## Related task pages {% related-card-grid title="Related task pages" %} - [Product Quickstart](/docs/quickstart) - [Project Context](/docs/agent-setup/project-context) - [Request an Expert Contribution](/docs/expert-contributions/request-contribution) {% /related-card-grid %}