# User Management

When you sign up to FlowMate, a unique FlowMate tenant will be created for your organization. All your users, templates, flows, and other resources will be contained in this tenant. In addition to the tenant, a number of partner accounts will also be created for you. In practice, there are two types of accounts in FlowMate:

### Partner Accounts

Partner Accounts are created by FlowMate when you first sign up or upon request. These are considered to be tenant admins and have wide-ranging permissions to read, create, edit, and delete nearly all tenant-level resources. These accounts are intended to manage templates, users, logs, etc. in order to maintain and monitor FlowMate usage.

Care should be taken when modifying resources created and owned by end-user accounts, as this can lead to unexpected behavior or states on their side.

### End-User Accounts

End-User Accounts can be created by partner accounts using the `impersonate` endpoint. These accounts are intended to actually create, configure and run flows based on templates. Their permissions are much more constrained, having only read access to most tenant resources, and write access only to resources such as flows or credentials created and owned by themselves.

For more information on creating and impersonating end-user accounts, check out the article on [Embedding the Integration Center](/flowmate-documentation/integration-center/embed-integration-center.md)


---

# Agent Instructions: 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:

```
GET https://flowmate.gitbook.io/flowmate-documentation/technical-fundamentals/user-management.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.