> 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/files/custom-styling.md).

# Custom styling

A file (such as a document or a clause) can have custom styling attached to it. This means that the file will **deviate from the default styling settings** configured by the customer (the user’s organisation), the user’s group(s) or the user’s own styling settings.

{% hint style="danger" %}
Because a file’s custom styling always deviates from the default styles, custom styling should only be added when absolutely necessary.
{% endhint %}

Both documents and clauses can have custom styling. If both the document where the clause is inserted and the clause itself have custom styling, the clause’s custom styling will take precedence in case of any conflicting style settings.

## How to add or edit custom styling

The custom styling settings of a file are accessed by opening the file by:

* double clicking it or clicking the edit button in the Browse Files mode;
* double clicking a clause in Assemble Document;
* editing the properties of a document when it is opened in Assemble Document or by accessing its properties when it is part of a binder (under the tab binder > advanced > properties)


---

# 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/files/custom-styling.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.