> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/feature-documentation/important-foundations/licences.md).
# Licences
Licences **affect which features are available** to you.
### Choose your licence
When you start work on an exercise, choose the licence you're designing for. This means if your organisation has several licences and they're not all the most feature-rich licences, you can limit yourself and not add features to your exercise that won't be available.
**A licence corresponds directly to a simulation space** so you should upload the exercise to the space associated with the licence.
Your personal test space will have all the features (as it does now) so you can always try new things.
### Licence details
Use the **spyglass icon** on the licence drop-down to see what features are available, the renewal date and when the connected simulation space was last updated.
---
# 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://helpdocs.conducttr.com/feature-documentation/important-foundations/licences.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.
