> For the complete documentation index, see [llms.txt](https://developers.gurupay.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.gurupay.eu/getting-started/guides/accounts-and-customers.md).

# Accounts and customers

This page outlines how company accounts and user access are managed within the platform.

**Company Account**

At Guru Pay, we provide **dedicated accounts**, meaning all accounts are issued under your company's name.\
If you need to open additional accounts, please contact our Client Care team for assistance.

#### Customers and User Access

Each user with access to the Guru Pay dashboard can be assigned to multiple customers. For example, if you're part of an IT team managing a group of companies, you can oversee all associated customers using a single login.

**Note:**

* A single customer can have multiple users assigned.
* However, only **one user** per customer will have **admin (Main user) rights**, which include permissions to set the Webhook URL and generate an API token.

To add new users, please contact our Client Care team at <clientcare@gurupay.eu>.\
As an account administrator, you're responsible for keeping user access up to date and ensuring permissions remain accurate.


---

# 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://developers.gurupay.eu/getting-started/guides/accounts-and-customers.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.
