# 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: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.clause9.com/getting-started/structuring-your-clause-library.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.