---
id: project-settings.general
title: General Project Settings
summary: Manage the project name and Project Memo without confusing descriptive metadata with agent context.
kind: reference
product_area: project_settings
status: stable
updated: 2026-09-07
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, or Review Screens. Put agent-facing operating context in Agent Setup.

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 evidence.

## 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 |
| Contribution-specific review behavior | Expert Contribution | Keeps behavior visible in the scoped request |
| 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 |
| Scoring behavior for future Benchmark Versions | Regime | Keeps the evaluation contract versioned and inspectable |

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 evidence 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. A grounding rule lives in the candidate Harness or governed policy, not in the memo.
{% /example-demo %}

{% related-card-grid title="Agent-facing configuration" %}
- [Configure Project Context](/docs/agent-setup/project-context)
- [Manage Harnesses](/docs/assets/harnesses)
{% /related-card-grid %}

## Related task pages

{% related-card-grid title="Related task pages" %}
- [Configure Project Context](/docs/agent-setup/project-context)
{% /related-card-grid %}

## Source confidence

Code-backed: the active General settings route defines the editable name and Project Memo and explicitly distinguishes the memo from prompt context.