> For the complete documentation index, see [llms.txt](https://help.clause9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clause9.com/getting-started/structuring-your-clause-library.md).

# Structuring your clause library

There are three levels to Clause9 clause libraries:

* an **organisation-wide library** that is accessible to every user of the customer’s company / law firm, even if some users may not have editing rights
* a **group-based library** for, for example, different departments or cross-departmental practice groups that can only be seen and accessed by members of the group
* a **private library** that is only accessible to an individual user

Deciding how to structure your clause libraries and where to put your clauses is a strategy that will have to be decided at administrator-level. The following is a list of important questions that need to be asked at the outset in that regard:

* Is it your intention to make certain clauses available and **usable across the entire organisation**? Or will you be creating separate silos for different departments? (See also the [FAQ on the viability of such wide sharing](/clauses/clauses-faq.md#can-the-same-clause-be-used-throughout-my-organisation)). 
* Who will have the responsibility to vet clauses that enter the organisation-wide library or group-wide library? 
* Who will be given which access rights? Can everyone access and edit? Or are editing rights limited to a group of more experienced users? 

It is important to assign the proper roles to the right people so that the entire organisation is aligned on how to use Clause9. 


---

# 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://help.clause9.com/getting-started/structuring-your-clause-library.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.