> ## Documentation Index
> Fetch the complete documentation index at: https://support.affinity.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Make Affinity AI Work Your Firm's Way

> Roll Ascend out to your team, write the instructions every meeting brief follows, describe your fields so suggestions arrive in your format, and build the review habit that keeps the CRM current.

***

## Immediate Value

By the end of this tutorial, every meeting brief your firm gets will stress what your partners care about, the Data Update agent will suggest values in your team's own format, and you'll have a simple weekly routine for checking that the agents are doing useful work.

## Prerequisites

* **Put Affinity AI to Work complete.** You've generated a brief and reviewed a suggestion yourself. See [Put Affinity AI to Work](https://support.affinity.co/s/article/Tutorial-AI-affinity-agents-and-ai-chat.md).
* **Scale, Advanced, or Enterprise.**
* **For Tasks 1 and 2:** the **Manage Affinity AI feature access** permission. **Admins** and **Enterprise Admins** have it by default; an admin can grant it to others on the Users and Permissions page.
* **For Task 3:** permission to edit the settings of your list's custom fields, in **New Lists**.

## Quick-Start Roadmap

| Task | What you'll do |
| :- | :- |
| 1 | Check Ascend is on, and tell your team the one thing they need to do |
| 2 | Write the instructions every meeting brief follows |
| 3 | Describe your key fields so suggestions arrive in your format |
| 4 | Make reviewing suggestions a team habit |
| 5 | Check the results and tune your context |

***

## Why Firm Context Matters

Ascend agents come with built-in private capital knowledge, but they don't know how *your* firm works: what a field means, the format a value takes, or what your partners want stressed before a meeting.

Two settings add that context. **Meeting Prep instructions** shape every brief for everyone in your organization. **Field descriptions** tell the **Data Update** agent what each custom field means and the format it expects.

Neither changes who's in control. No instruction can make an agent write to your CRM on its own: every Data Update suggestion still waits for a person to accept it.

***

## Task 1: Check Ascend Is On, and Tell Your Team the One Thing They Need to Do

### Context

Ascend has been on by default since August 5 for every firm that didn't opt out. But switching it on for the organization does **not** switch **Monitoring** on for anyone: each member turns it on for themselves. A rollout that skips this step leaves Ascend empty for most of the team.

### Action

1. Go to **Settings → Automations & AI → Affinity AI** and find the **Ascend** card. If it isn't enabled, click **Edit**, choose **Enable**, and click **Save**.
2. Tell your team the one thing to do: open **Ascend → Agents** and switch **Monitoring** on for **Meeting Prep** and **Data Update**.
3. Tell them they can try it first without changing anything: on any upcoming external meeting, click **Generate Brief**.

> [!NOTE]
>
> All settings on the **Affinity AI** page are org-wide. There are no role-, team- or user-level controls for which AI features are available.

### Expected Outcome

Ascend is available to your firm, and your team knows to turn Monitoring on for themselves.

### 📚 Help Center

* [Enabling Affinity Ascend — An Admin's Guide](https://support.affinity.co/s/article/Enabling-Affinity-Ascend.md)
* [Set up and configure your agents](https://support.affinity.co/s/article/Set-up-and-configure-your-agents.md)

***

## Task 2: Write the Instructions Every Meeting Brief Follows

### Context

**Agent Instructions** on the **Meeting Prep Agent** card apply to every brief generated after you save — the automatic overnight briefs and the ones anyone generates on demand, for every user. There's one set for the whole organization.

### Action

1. Open **Ascend → Agents**. (Or start from **Settings → Automations & AI → Affinity AI**: on the **Ascend** card, next to **Agent instructions**, click **Manage**.)
2. On the **Meeting Prep Agent** card, find **Agent Instructions** and click **Edit**.
3. Write your instructions, up to **2,000 characters**. Instructions work best for style and emphasis — what to include or leave out, how to lay it out, and what to stress. For example:
   * *"Include only a high-level summary of the meeting purpose and key questions to ask."*
   * *"Use bullet points, and keep each section short."*
   * *"For investor meetings, lead with fundraising history and current investors."*
4. Click **Save**.
5. Generate a brief for an upcoming external meeting and check it follows your instructions.

> [!TIP]
>
> If a brief ignores an instruction, reword it as something to **include**, **leave out** or **emphasize**. An instruction that reshapes the whole brief, such as a fixed length, may not be followed. Briefs generated before you saved aren't rewritten.

Everyone in your organization can read the instructions on the **Meeting Prep Agent** card (**View more** shows the full text), so nobody's briefs change without the reason being visible.

### Expected Outcome

Every new brief at your firm follows the same house style.

### 📚 Help Center

* [Give Ascend agents your firm's context](https://support.affinity.co/s/article/Give-Ascend-agents-your-firms-context.md)

***

## Task 3: Describe Your Key Fields So Suggestions Arrive in Your Format

### Context

The **Data Update** agent has no instructions box. Its context comes from **field descriptions**: when it reads a meeting note, it also reads the description of each field it considers. Suggestions follow the description, or the agent leaves them out.

Start with the five or six custom fields your team updates after every meeting — stage, round size, deal lead, next step.

### Action

1. Open a list in **New Lists**.
2. Click a custom field's column header and choose **Edit field**.
3. In the description box under the field name — *"Add a field description for Affinity agents to use."* — say what the field means and the format it expects, in up to **255 characters**. For example:
   * **Round Size** — *"Round size in millions of USD. Enter 14, not 14000000."*
   * **Scouting Description** — *"A one-line tagline, under 15 words."*
   * **Deal Lead** — *"The partner leading the deal, not the associate."*
4. Click **Save**.

> [!NOTE]
>
> Descriptions are for **custom fields** in **New Lists**; enriched and system fields don't take one. A description also shows to teammates when they hover over the column header — so it explains the field to new joiners, too.

### Expected Outcome

Your key fields say what they mean, and the agent's suggestions arrive in the format your team uses.

### 📚 Help Center

* [Give Ascend agents your firm's context](https://support.affinity.co/s/article/Give-Ascend-agents-your-firms-context.md)
* [How to create and delete fields in New Lists](https://support.affinity.co/s/article/How-to-create-and-delete-fields-in-new-lists.md)

***

## Task 4: Make Reviewing Suggestions a Team Habit

### Context

Suggestions only keep the CRM current if someone decides on them. Each set goes to the person who created the meeting note. A two-minute review after each external meeting — or once at the end of the day — is the habit that keeps records current without anyone doing admin.

### Action

1. Open **Ascend → Review**. Suggestions are grouped by the record they affect.
2. Click **Review** on an item. **Ascend Chat** opens full screen, with a **Suggested field updates** panel next to the conversation.
3. For each field, compare the **Current Value** and the **Suggested Value**. To correct one, click the value and change it — it's marked **Suggested Value (edited)**, and **Reset** puts the agent's suggestion back.
4. Click **Accept** or **Dismiss** on each field, or **Accept All** / **Dismiss All** on the card. Fields you haven't decided on wait for you; the card shows how many are left.

> [!WARNING]
>
> Check a suggestion against its source (**View Note**) before you accept it. What was said in a meeting isn't always what was decided.

### Expected Outcome

Your team reviews suggestions as part of their day, and accepted values appear on records like any other edit.

### 📚 Help Center

* [Review and approve agent suggestions](https://support.affinity.co/s/article/Review-and-approve-agent-suggestions.md)

***

## Task 5: Check the Results and Tune Your Context

### Context

Firm context is never finished. The fastest signal is what your team dismisses: a field that's dismissed again and again usually needs a clearer description, and a brief section nobody reads usually needs an instruction to leave it out.

### Action

1. Open **Ascend → History**. Decided suggestion sets live here (**View Updates**), with briefs (**View Brief**) and the notes they came from (**View Note**).
2. Look for patterns over a week or two: the same field dismissed, values edited into the same format, or a brief section your partners skip.
3. Fix the cause, not the symptom — tighten that field's description (Task 3), or add an instruction to include, leave out or emphasize something (Task 2).

### Expected Outcome

Your firm's context gets a little sharper every few weeks, and the agents' output gets more useful with it.

### 📚 Help Center

* [Review and approve agent suggestions](https://support.affinity.co/s/article/Review-and-approve-agent-suggestions.md)

***

## Common Questions

> [accordion] Can instructions let an agent change our CRM without approval?
>
> No. Instructions shape what an agent produces, not what it's allowed to do. Every Data Update suggestion still needs a person to accept it.

> [accordion] Can each user set their own Meeting Prep instructions?
>
> No. There's one set for the organization, written by people with the **Manage Affinity AI feature access** permission.

> [accordion] Can I add a field description in Classic Lists?
>
> No. The description box is only in New Lists.

> [accordion] Does a description stop the agent from suggesting a field?
>
> No. A description explains a field; it doesn't block it. If a suggestion shouldn't be applied, click **Dismiss**.

***

## What's Next

With the agents set up your firm's way, decide what else your organization allows — AI tools over MCP, OAuth apps, Notetaker retention — in [Govern AI, Integrations and Usage](https://support.affinity.co/s/article/Tutorial-AI-govern-ai-integrations-and-usage.md).

*Affinity AI can make mistakes. Review each suggestion before approving it.*


## Related topics

- [Govern AI, Integrations and Usage](https://support.affinity.co/s/article/Tutorial-AI-govern-ai-integrations-and-usage.md)
- [Affinity MCP Skills](https://support.affinity.co/s/article/Affinity-MCP-skills.md)
- [Put Affinity AI to Work: Agents and AI Chat](https://support.affinity.co/s/article/Tutorial-AI-affinity-agents-and-ai-chat.md)
- [Working a conference attendee list against your firm's network ](https://support.affinity.co/working-conference-attendee-against-network.md)
- [Warm Intros in AI Chat and MCP](https://support.affinity.co/s/article/Warm-Intros-in-AI-Chat-and-MCP.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.