> For the complete documentation index, see [llms.txt](https://docs.tuplo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tuplo.com/tuplo-account-management-guide/your-tuplo-dashboard/preferences/durations.md). # Durations Configure time-based parameters for interactions and transactions on your website.

Durations apply timed limits to different elements related to your customer's activity. These include: * **Account Sign-In**: Determines how long before a user needs to reenter their login information to sign back in. * **Account Sign-up**: Determines how long a user can take during sign-up after receiving an invite. * **Account Invite**: Controls how long an invite link is valid before expiring. * **Accounts Update**: Controls how long an update link is valid before expiring. *** ## Define Durations To **adjust** duration times: 1. **Enter** the desired amount into the applicable text field. 2. **Choose** the unit of time from the drop-down menu. 3. **Click** the Update Durations button to apply the 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://docs.tuplo.com/tuplo-account-management-guide/your-tuplo-dashboard/preferences/durations.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.