> 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/clauses/how-to-clauses/make-a-paragraph-within-a-clause-conditional.md).

# Make a paragraph within a clause conditional

To show or hide a paragraph or bullet, based on the (non-)fulfillment of a condition, follow these steps:

1. type the paragraph number or bullet asterisk
2. write the condition elements based on which the text will appear or disappear
3. write the text of the paragraph/bullet

In practice, that could look something like this:

{% code overflow="wrap" %}

```
1. This paragraph is not conditional.
2. {#employee^name = "John": This paragraph is only shown if the employee's name is John.}
* {#employee^function = "CEO": This bullet is only shown if the employee is the CEO}
```

{% endcode %}

{% hint style="warning" %}
Make sure not to put the number or asterisk preceding the text of the paragraph or bullet, respectively, inside the condition, as Clause9 will be unable to recognise that these symbols mean the start of a paragraph or bullet and will instead think they are merely ordinary text. 
{% endhint %}


---

# 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/clauses/how-to-clauses/make-a-paragraph-within-a-clause-conditional.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.