> For the complete documentation index, see [llms.txt](https://docs.tactyc.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tactyc.io/sharing-and-administration/collaborators.md).
# Collaborators
Collaborators are team members who have access to your fund's model. You can control access levels for collaborators to only grant them read or edit access.
## Adding a Collaborator from Home
* From your home screen and click on the **Manage Collaborator** under **Collaborators** for your fund
* On the next dialog, enter the email address of the person you want to collaborate with
* Collaborators will get an email saying you’ve sent a model to them. Once they login to their Tactyc account they’ll see your model on their home screen.
## **Adding a Collaborator from with the fund's dashboard**
* Open the fund's dashboard
* From the left side-bar click on **Collaborators**
## **Set Access Levels for Collaborators**
* By default all collaborators have full-write access to all parts of your fund. You can control the access levels for different sections of the fund by collaborator.
**Note:** Collaborators must have an active Tactyc account. This may be a valid trial account as well.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.tactyc.io/sharing-and-administration/collaborators.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
