# Default styles

On the defaults page, you can set several default values:

## Default styles

You can select any styles created on the [styles page](/admin/styles.md) to be used as the default style throughout your organisation (i.e. for all users, groups and documents). (For a reminder on how Clause9 applies styles on multiple levels, please consult this article on styling.)

## Q\&A card colors

*(If allowed by your subscription plan)* You can set the default colors of Q\&A cards, for mutiple levels of cards (i.e. card that are indented).

## Custom home page

Instead of the standard welcome page, you can define a custom home page for all your users (except for users or group members for whom a deviating custom home page was selected). Check [Custom homepage](#custom-home-page) for more information about this subject.

## Custom CSS

*(If allowed by your subscription plan)* you can define custom “CSS” (*Cascading Style Sheets)* to completely restyle the way Clause9 looks. How this actually works, is beyond the scope of this help-page — but don’t be afraid, CSS is a standard web technology since many years, and there are hundreds of books available on this subject.

{% hint style="info" %}
Be aware that we do not guarantee that the CSS will remain unchanged throughout different releases of Clause9. When you define Custom CSS, you should therefore be prepared to occasionaly update the CSS to cope with small changes in the Clause9 user interface.
{% endhint %}


---

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