---
source: crewkit documentation
url: https://crewkit.io/docs/settings-map.md
title: "Settings map"
description: "The settings listed here, the level it applies at, who may change it, its default and what changing it stops."
---


A **setting** applies at one level: the organization, a project, a repository or a person. A lower level can narrow some organization settings, but cannot loosen any. This page lists each setting once, with its default, the lowest role that may change it and what changing it does.

Roles, from most to least privileged: Owner, Admin, Manager, Developer, Viewer. "Manager and up" means Manager, Admin or Owner. What each role reads is on [Team](/docs/team#roles).

---

## Organization

Changed in **Settings → Organization** unless the row says otherwise. These apply to every project and every member of the organization.

| Setting | Default | Who changes it | What changing it does |
|---|---|---|---|
| **Capture Mode** (`capture_mode`), on the **Privacy & Telemetry** card | `structured` | Admin and up | Decides how much session content crewkit collects; see [Capture modes](/docs/capture-modes). Moving to `minimal` also strips the text of stored pull request and issue records. |
| **Data Retention Period** (`retention_days`), same card | 365 days | Admin and up, between 7 and 365 days | Session content older than this is deleted by the next retention sweep. |
| **Default language** (`default_locale`) | English | Manager and up | The organization's default language, English or French. |
| **Email subjects** (`minimal_subjects`) | off | Manager and up | Decides what a notification email shows on a lock screen before anyone opens it. |
| **Asks** opt-in, with **Asks: keeping Responses** (`asks_response_retention_days`) and **Asks: never send outside** | off; 180 days | Admin and up | Turns [Asks](/docs/asks) on or off, sets how long Responses are kept (30 to 365 days) and the names that must not leave the organization, such as clients and codenames, which the text check flags before an Ask is published. Choosing a new Asks domain asks for a fresh dashboard sign-in. |
| Managers may publish Asks (`asks_managers_may_publish`) | off | Admin and up | While off, only an Admin or Owner publishes an Ask. |
| **Feedback** opt-in, retention (`feedback_retention_days`) and session triage (`feedback_session_triage_enabled`) | off; 180 days; off | Admin and up | Turns [Feedback](/docs/feedback#turning-feedback-on) on or off and sets how long reports are kept (30 to 365 days). Session triage can be turned on from the dashboard only, never from a CLI token. |
| Data residency, on the **Data Plane** card | hosted | Admin and up, on a plan that includes it | Moves session content to the organization's own data plane; see [Data residency](/docs/data-residency#who-turns-it-on). |
| Session links | Session messaging off | Admin and up | Decides whether sessions can link and message each other; see [Session messaging](/docs/session-messaging#for-organization-admins). |

### API only

These organization settings have no dashboard control. An Admin or Owner changes them with `PATCH /api/v1/<org>/telemetry/settings`.

| Setting | Default | What changing it does |
|---|---|---|
| `retain_prompts`, `retain_tool_calls`, `retain_responses`, `retain_tool_results` | all on | Turning one off stops crewkit writing that category of transcript content down, and hides what was already written from transcripts, the API and share links. |
| `correction_analysis_enabled` | off | Turning it on allows correction detection on the organization's conversations. |
| `plane_derived_rows_enabled` | off | For a resident organization: whether its data plane may send per-session scores and token counts back to crewkit. |

---

## Project

Changed in the project's **Settings** unless the row says otherwise.

| Setting | Default | Who changes it | What changing it does |
|---|---|---|---|
| Name, Jira key, Slack channel ids | none | Manager and up; a workspace's lead may rename it and change its Jira key and work Slack channel | Renames the project, and sets where [work items](/docs/workspaces) find Jira cards and post to Slack. Creating a project takes Developer and up; deleting one, Admin and up. |
| Presence | follows the organization | Manager and up | Narrows who sees live sessions on this project. It cannot widen the organization's setting. |
| Playbook assignments | none: the organization's playbooks apply | Manager and up to add, Admin and up to remove | Scopes which [playbooks](/docs/playbooks) apply to this project. |
| **Feedback keys** | none | Developer and up to create; Manager and up, or the key's own creator, to revoke | A revoked key stops accepting reports. See [Feedback keys](/docs/feedback#feedback-keys). |
| Feedback daily cap (`feedback_daily_cap`) | 200 per day | Manager and up, from 1 to 1,000, with the MCP tool `set_feedback_daily_cap` | The most reports the project accepts in a UTC day. |

### What you cannot set per project

- **Capture mode**
- **Retention**
- **Data residency**

Each is set once for the whole organization; a project has no setting for any of them. The narrower controls are a repository's session visibility (below) and a [sensitive session](/docs/sensitive-sessions). Ask an Admin or Owner to change the organization's setting.

---

## Repository

| Setting | Default | Who changes it | What changing it does |
|---|---|---|---|
| Session visibility: Public, Restricted or Private | Public | Manager and up for Public or Restricted; Admin and up for Private. Through the API only | Hides conversations in that repository from lower roles and keeps them out of analysis and project search; see [What feeds analysis](/docs/capture-modes#what-feeds-analysis). |

---

## Person

| Setting | Default | Who changes it | What changing it does |
|---|---|---|---|
| Sensitive session (`crewkit code --sensitive`) | off | The person, per launch | Marks that one session sensitive; see [Sensitive sessions](/docs/sensitive-sessions). |

---

## Set by crewkit, not by your organization

- **Lessons.** An organization gets [Lessons](/docs/lessons) only when a crewkit platform owner turns it on for that organization. No one in your organization can turn it on. Ask crewkit support.

## Next steps

- [Integrations](/docs/integrations-setup): what each connected tool reads and writes, and who connects it.
- [Team](/docs/team): roles and what each reads.
