> 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/admin/general.md).

# General

If you are logged in as the administrator account of your organisation, you will see a tab “admin” in the top navigation bar. 

On the admin page, you can do (among others) any of the following to manage your organisation’s account:

* [manage your organisation’s users:](/admin/users.md)
  * create or delete users
  * change a user’s e-mail address
  * give a user additional rights or take rights away
  * manage a user’s default styles or language preferences
* [manage your organisation’s groups:](/admin/groups.md)
  * create groups (with or without a separate library) or delete groups and manage group memberships
  * manage default styles on group level
* [manage standard styles for your organisation](/admin/styles.md) (styles which your users or groups can choose from when editing documents)
* [manage default styles for your organisation](/admin/default-styles.md) (styles that will automatically be applied to any document)
* create, edit or delete [attribute models](/admin/attribute-models.md)
* [monitor usage](/admin/usage-page.md) of Clause9 by your organisation’s users


---

# 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/admin/general.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.