> 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/file-position.md).
# File position
“Position” is one of the properties of clause files. It can be used to suggest the appropriate positioning of a clause to users of the clause.
{% hint style="info" %}
An example of good use of preferred positioning of a clause is a clause containing a signature block, which should in most cases be positioned at the very end of a document.
{% endhint %}
## How ‘position’ works
A clause can be assigned an (approximate) preferred position within a document. Five types of preferred positions are possible:
* at the very beginning of a document
* towards the beginning
* somewhere in the middel
* towards the end
* at the very end
When a preferred position has been assigned to a clause, a user wanting to insert that clause in his/her document will be able to choose “automatic position” instead of the standard options for inserting clauses.
“Automatic position” will be suggested when inserting a clause with a preferred position.
## How to assign a preferred position to a clause
When editing a clause, navigate to *Position* in the navigation menu on the right hand side. You can now select one of the five options listed above for your clause.
Dropdown list to choose a preferred position.
If you want the clause to no longer have a preferred position, pick choose “N/A”.
Hit to save your changes.
---
# 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/file-position.md?ask=&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.
to save your changes.
---
# 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/file-position.md?ask=