> For the complete documentation index, see [llms.txt](https://docs.finops.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finops.softwareone.com/insights/pools/pool-constraint-policies.md).
# Create pool constraint policies
If you want to implement policies for an entire pool, instead of a single resource, you can do so from the **Constraints** option within the pool's details page.
Only individuals with a **Manager** role can enforce shared constraints across the pool. While shared constraints apply pool-wide, custom resource-specific constraints can still be configured and will override the general policy.
### Create a pool constraint policy
To configure pool constraint policies:
1. Navigate to the **Pools** page.
2. Select the desired pool group or subpool.
3. Go to the **Constrains** tab and select the edit icon.
4. Enter values in the **TTL** (Time-to-live) or **Daily expense limit** fields.
5. Select to save your changes. The constraint will apply to the resources within the selected pool or subpool.
Pool constraint policies.
{% hint style="info" %}
A constraint will not be visible if the related resource has already been deleted from FinOps or if a resource has been tracked only by imported billing data.
{% 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 dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.finops.softwareone.com/insights/pools/pool-constraint-policies.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 `build a script that syncs our docs to a CMS` 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. The constraint will apply to the resources within the selected pool or subpool.