> For the complete documentation index, see [llms.txt](https://docs.plextrac.com/plextrac-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plextrac.com/plextrac-documentation/product-documentation-1/account-management/account-admin/licensing/priorities.md).
# Priorities
This option determines if a priority applies to a tenant or is specific to a client and whether it appears to end users after creation. The default value is `Tenant-level priorities`.
{% hint style="warning" %}
Modifying this option *after* users have created priorities can change the priorities displayed on the **Priorities** module home page. Priorities assigned to specific clients will not be shown if the tenant is set to "`Tenant-level priorities.`"
{% endhint %}
## Tenant-level Option
If `Tenant-level priorities` is selected, a user can set up a priority across all clients in the tenancy with access to all findings and assets in the platform.
This will be identified to users in the Priorities module home page under the "Client" column as `All clients`.
## Client-level Option
If `Client-level priorities` If selected, a user must choose a client when creating a priority and can only link assets and findings from that client.
This will be identified to users in the Priorities module home page under the "Client" column by listing the client's name.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.plextrac.com/plextrac-documentation/product-documentation-1/account-management/account-admin/licensing/priorities.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
