> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/support/user-permissions-and-administration/how-to-create-and-manage-users-teams-and-permissions/limio-support-and-user-creation-in-customer-production-environments.md).

# Limio Support and User Creation in Production

To ensure customer security, uphold data integrity, and maintain the principle of least privilege, **Limio Support does not have permission to create users in customer production environments**. The creation and management of users in production environments are the sole responsibility of the customer’s environment administrators

**Why Limio Support Cannot Create Users in Production**

* **Security and Compliance**\
  Production environments often contain sensitive data. Minimising access helps reduce potential security risks.
* **Data Integrity**\
  Managing users in production requires strict controls to prevent unintentional disruptions. User creation is a critical action best handled by the customer.
* **Industry Best Practices**\
  External support teams are generally limited in their access to production systems to reduce risks and maintain compliance with industry standards.

**Customer Responsibilities**

To effectively manage users in your production environment, ensure the following:

* **User Management**\
  Administrators are responsible for creating, modifying, and deleting user accounts.
* **Admin Access**\
  Ensure that there are an adequate number of administrators with the necessary permissions to perform user management tasks.

#### **How Limio Support Can Assist**

While Limio Support cannot directly create users in production environments, we can assist with various aspects of user management:

* **Guidance and Troubleshooting**
  * Assistance with questions about the user creation process.
  * Diagnosis and resolution of issues related to user access.
* **Configuration Advice**
  * Recommendations for configuring user permissions and roles.
  * Best practices for secure user management.
* **Training Resources**
  * Access to training materials or sessions to familiarise your team with user management tasks.

***

### Further Resources

For more guidance on user management, explore additional resources in our [Users and Permissions](/support/user-permissions-and-administration/how-to-create-and-manage-users-teams-and-permissions.md).


---

# 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.limio.com/support/user-permissions-and-administration/how-to-create-and-manage-users-teams-and-permissions/limio-support-and-user-creation-in-customer-production-environments.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.