> For the complete documentation index, see [llms.txt](https://vampauth.gitbook.io/vampauth-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vampauth.gitbook.io/vampauth-docs/features/project-settings.md).

# Project settings and flow URLs

| Setting                 | Accepted range                |
| ----------------------- | ----------------------------- |
| Default key duration    | 60–31,536,000 seconds         |
| Maximum keys per person | 1–10                          |
| User resets per key     | 1–20, or null for unlimited   |
| Stack cooldown          | 0–86,400 seconds; default 600 |
| Loader leases           | On/off                        |
| Concurrent keyed leases | 1–10; default 1               |

Concurrent sessions are runs, not extra device bindings. The binding policy stays one device per key.

## Readable flow URLs

A Pro project can claim `https://vampauth.com/myhub/flow`. The original project-ID link still works.

Names are globally unique while assigned. Use 3–32 lowercase letters, digits, or hyphens; start and end with a letter or digit. App routes, generated-ID formats, and existing URL reservations aren't available.

Renaming claims the new name and releases the old one. If the replacement is taken, the current name stays. Removing a name or deleting the project releases it.

When Pro expires, the custom link pauses and the name stays reserved. Renewal restores it. Use the original ID-based URL while paused. Released names don't redirect to their former project.

Manage this in Project → Settings. Generic v2 project settings don't accept a custom-name field.


---

# 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://vampauth.gitbook.io/vampauth-docs/features/project-settings.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.