> For the complete documentation index, see [llms.txt](https://docs.cogram.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cogram.com/settings/insight-preferences.md).

# Insight Preferences

Insight Preferences tell Cogram how to write your AI-generated insights: the tone, length, level of detail, and language used in summaries, bullet points, minutes, and your Custom Insights.

Preferences change **how existing insights are written**. To add a new output (a follow-up email, a translated summary), use [Custom Insights](/settings/custom-insights.md) instead.

## When to use this

* Your minutes are too long, too short, or too informal for your client
* You want consistent terminology across a project team
* You want insights written in another language
* One insight type needs different treatment from the rest

## Set your own preferences

1. Open the avatar menu at the bottom of the left sidebar and go to [Account Settings > Meetings](https://app.cogram.com/dashboard/settings/account-settings/meetings).
2. Select **Insight preferences** in the left column.
3. Under **All insights**, describe how you want insights written. For example: `Write in a formal tone. Use UK spelling. Keep summaries under 200 words and lead with decisions.`
4. Select **Save**.

Each preference holds up to 4,000 characters.

**Expected result:** meetings processed from now on follow the preference. Meetings Cogram has already processed keep the insights they have.

## Set a preference for one insight type

Use this when only one output needs to change: for example, minutes must stay formal while bullet points stay terse.

1. In the same section, go to **Per-insight preferences**.
2. Select **Add preference for...** and choose the insight type.
3. Enter the instruction and select **Save**.

Per-insight preferences apply on top of your **All insights** preference.

## Organization and group preferences

Preferences exist at three levels, and a meeting uses all of them together:

| Level        | Who sets it  | Where                                                                                                                        |
| ------------ | ------------ | ---------------------------------------------------------------------------------------------------------------------------- |
| Organization | Admins       | [Organization Settings > Meetings](https://app.cogram.com/dashboard/settings/admin/meetings) → **Insight preferences**       |
| Group        | Group Admins | [Group Settings](https://app.cogram.com/dashboard/settings/group/all) → your group → Meetings → **Insight preferences**      |
| Personal     | Each user    | [Account Settings > Meetings](https://app.cogram.com/dashboard/settings/account-settings/meetings) → **Insight preferences** |

Cogram sends all applicable preferences to the AI together, in the order organization, then group, then personal. They combine rather than replace each other, so keep them short and avoid contradicting a level above you: if the organization asks for formal language and you ask for casual, the result is unpredictable.

Preferences you inherit are listed read-only under **Inherited preferences**, so you can see what already applies before adding your own.

Group preferences reach a user through their **settings group**: the one group whose settings cascade to them. See [Groups](/administration/groups.md).

> Cogram's insights are AI-generated drafts. Always review names, dates, decisions, action items, and technical values before issuing minutes, whatever preferences you set.

## Troubleshooting

**An existing meeting still shows the old wording**

*Likely cause:* preferences apply when insights are generated. Saving a preference does not rewrite meetings Cogram has already processed.

*Fix:* apply the preference to future meetings, or copy the insight and edit it by hand for this one.

**A colleague's meeting ignores my personal preference**

*Likely cause:* Cogram applies the preferences of the meeting's owner, not the person reading or downloading it.

*Fix:* set the preference at organization or group level so it applies to everyone's meetings.

**Emptying the box does not clear the preference**

*Likely cause:* **Save** stays unavailable while the field is empty.

*Fix:* select **Remove** to delete the preference.

**The preference seems to be ignored**

*Likely cause:* preferences at all three levels are combined, and a long organization preference can crowd out shorter ones.

*Fix:* shorten the instruction, make it specific ("Use UK spelling"), and check **Inherited preferences** for a conflicting instruction set above you.

## Next steps

* [Custom Insights](/settings/custom-insights.md): create new AI outputs rather than reshaping existing ones
* [Templates](/settings/templates.md): control which insights appear in your exported minutes


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cogram.com/settings/insight-preferences.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.