> For the complete documentation index, see [llms.txt](https://docs.auditchain.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.auditchain.finance/luca-suite/collaboration.md).

# Collaboration

Add teams to your workflow

Now you can share and work with legal counsel, accounting, engineering and your ESG teams on the same disclosure model and each disclosure. 

The collaborative features revolutionize compliance processes by enabling real-time multi-user editing, automated version tracking, and integrated feedback loops. 

<figure><img src="https://2327119718-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MTcBaZfgA6Ge46uqCCB%2Fuploads%2FyiGy77qsb9VJ5W6vjJOl%2Fcollaborate-mica-pacioli.png?alt=media&amp;token=9d58a5e1-385e-4c6e-b643-75e7399009a4" alt=""><figcaption></figcaption></figure>

These tools save time through streamlined workflows, eliminating sequential reviews and reducing turnaround from days to hours.&#x20;

Cost savings arise from minimized manual labor and avoidance of costly compliance fines.&#x20;

Errors are eliminated via collective scrutiny and audit trails, while risks diminish through enhanced accuracy, traceability, and proactive issue resolution.&#x20;


---

# 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.auditchain.finance/luca-suite/collaboration.md?ask=<question>&goal=<user_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.