> For the complete documentation index, see [llms.txt](https://docs.squads.so/main/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.squads.so/main/navigating-your-squad/settings/time-locks.md).

# Time Locks

Time locks allow Squad members to defer the execution of approved transactions for a set period of time.

* Time locks apply globally to all Squad transactions once set.
* "Active" transactions and "Ready" transactions for changing Squad settings initiated before the time lock will change to a "Canceled" state upon activation.
* Available periods: 1 hour, 1 day, 1 week, Custom (in seconds), None (disables the time lock).

To create a time lock:

1. Navigate to the "Settings" tab.
2. Select the desired time lock period and initiate a transaction.
3. The time lock activates upon transaction execution.

{% hint style="info" %}
Choose a time lock duration that balances security with accessibility of funds. Avoid excessively long periods (e.g. 1 month) if regular asset management is expected.
{% 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://docs.squads.so/main/navigating-your-squad/settings/time-locks.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.