> For the complete documentation index, see [llms.txt](https://handbook.n8n.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.n8n.io/how-we-enable/how-we-enable/request-a-team-n8n-instance.md).

# Request a team n8n instance

Request a dedicated team instance when the all-company internal instance is no longer reliable enough for your workflows, when your team has business-critical workflows that would be disrupted by maintenance or experimentation downtimes.

You are responsible for maintaining your team's instance. A new instance does not include preconfigured credentials. Coordinate with the relevant tool owners to get the credentials your workflows need.

## Before you request an instance

Check whether your team can use an existing team instance first. Sharing an instance avoids another environment that a team must own and maintain.

If your team needs its own instance, prepare:

* A team or group email address. This address will own the instance. If your team does not have one, [create a Google Group](https://groups.google.com/all-groups) or ask the People team for a team email.
* A preferred instance name. It becomes part of the URL for the new n8n Cloud instance. Check that the name is available before making the request.

## Make the request

Contact the Automation team with the team or group email address and preferred instance name.

The Automation team will:

1. Create the instance license key and add it to the n8n account in Salesforce, which is the system of record for license keys.
2. Trigger deployment of the new Cloud instance.
3. Invite you to [Manifest](https://manifest.n8n.io/), where you can connect the team instance as a data source for automations.


---

# 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://handbook.n8n.io/how-we-enable/how-we-enable/request-a-team-n8n-instance.md?ask=<question>&goal=<endgoal>
```

`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.