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

![Teamwork CRM logo](/logos/integrations/teamworkcrm.webp)

Teamwork CRM may help you bring selected crm information into Lithi workflows, while credentials and private provider payloads remain outside the portal.

## What this connection helps you do

Use this connection when a reply would benefit from customer, team, or financial context that you already manage in Teamwork CRM. You decide which information matters, which task may use it, and how long that choice should remain active.

The connection is designed for focused context, not broad account visibility. Lithi can work with the information you choose to share, while your credentials and private provider payloads stay outside the portal.

## Information categories you choose to share

Choose only the information categories that fit the task:

- **Contacts** information
- **Accounts** information
- **Opportunities** information
- **Activities** information
- **Leads** information

These labels are plain categories, not a promise about a particular account. The information you choose should be limited to what a person needs for the intended reply or review.

## Connect in three clear steps

1. Choose the account and information categories that match the task.
2. Complete the connection on the signed-in connection surface, then review the information shown before continuing.
3. Keep the connection focused on the approved purpose and check the result before relying on it.

Your credentials remain with the connection surface. Lithi receives only the private, minimized context that you intentionally allow for the selected task.

## Narrow or remove access

You can narrow the information categories whenever the task changes. A smaller choice is often the clearest choice for a sensitive workflow.

To stop using the connection, remove its access from the connection surface or disconnect the account there. Removing access prevents future context from being offered, while deleting a local connection is a separate choice.

Review the visible account, category, and purpose before you confirm a change. If anything looks broader than intended, stop and return to the connection controls.

Keep credentials private, share the smallest useful context, and remove access when the purpose is complete. Review it again before a new task.