> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/pro/automation/accounts.md).

# Accounts (connections)

Accounts in the Equipme Pro automation module: create, test, rename and remove connections to Pro, ERP, PSA and customer tenants – securely and in the right area.

**Path:** "Automation" → "Accounts"

An **account** is a stored connection to a system – to Equipme Pro itself, to your ERP, to Autotask or to a customer's Microsoft tenant. You create it once and then select it in every matching component without signing in again.

## The account list

The list shows for each account:

| Column        | Content                                                                   |
| ------------- | ------------------------------------------------------------------------- |
| **"Name"**    | Name of the account                                                       |
| **"Service"** | The connected system, e.g. Equipme, weclapp or Microsoft                  |
| **"Usage"**   | In how many flows the account is used, e.g. "Used in 3 flows."            |
| **"Status"**  | Result of the last test: "Tested" (OK), "Failed" (faulty) or "Not tested" |

Use "Filter …" to search by name. The list shows the accounts of the selected area "Personal" or "Team".

## Creating an account

You create accounts in the [flow designer](https://hub.equipme.io/pro/automation/flow-designer.md) as soon as a component needs a connection:

1. Drag the component onto the canvas and select it.
2. In the inspector, click **"Connect account"** or **"Connect a new account"**.
3. Sign in or enter credentials (see below). The account is checked and saved.
4. It then appears under "Accounts" and can be selected in all components of the same system.

Depending on the system, there are two ways of signing in:

* **Sign-in at the provider:** The system's sign-in window opens, e.g. Microsoft's. You sign in and confirm the requested permissions. You only enter your password at the provider.
* **API key or credentials:** You enter a key that you generated in the respective system, e.g. in weclapp or Autotask.

### Connection to Equipme Pro

For the components of the equipme connector you need an **API key from Pro**:

1. Generate an API key under ["Administration" → "Integrations" → "API key"](https://hub.equipme.io/pro/administration/integrations.md#api-key). Your tenant ID is shown there too.
2. In the flow designer, add a component of the "Equipme Pro" module, click "Connect account" and enter the API key.

Details: [equipme connector – Pro modules](https://hub.equipme.io/pro/automation/connectors/equipme-pro.md#setting-up-the-connection).

### Accounts per customer tenant

For [Microsoft Intune](https://hub.equipme.io/pro/automation/connectors/microsoft-intune.md) and [Microsoft Entra ID](https://hub.equipme.io/pro/automation/connectors/microsoft-entra-id.md), an account always applies to **exactly one tenant**. Therefore create **a separate account per customer** – signed in with an account in that customer's tenant – and give it a unique name, e.g. "Intune – Customer Sample Ltd".

## Managing accounts

| Action         | Effect                                                               |
| -------------- | -------------------------------------------------------------------- |
| **"Test"**     | Checks the connection of an account.                                 |
| **"Test all"** | Checks all accounts at once.                                         |
| **"Rename"**   | Gives the account an understandable name.                            |
| **"Revoke"**   | Removes the account and withdraws automation's access to the system. |

{% hint style="warning" %}
**Removing stops flows.** All flows that use a removed account are stopped. Check under "Usage" beforehand which flows are affected. Afterwards, select another account in these flows and restart them.
{% endhint %}

## "Personal" or "Team"

Like flows, accounts belong to an area (see [Automation at a glance](https://hub.equipme.io/pro/automation.md#choosing-the-area-personal-or-team)):

* **"Team":** Everyone with automation access can use the account in their flows. Right for productive connections such as ERP, PSA or Pro.
* **"Personal":** Only you use the account. Right for tests or connections with your personal account.

Create a flow and its accounts in the same area.

## Security

* **Service accounts instead of personal accounts:** Connect productive flows with a dedicated service account or API user. This way the flows keep running when a person leaves the company, and changes can be clearly attributed in the third-party system.
* **As few permissions as necessary:** Give the connected account only the permissions the flow needs.
* **Treat API keys like passwords:** Don't pass them on by email or chat. Delete keys you no longer need in Pro.
* **Check regularly:** Use "Test all" to detect faulty accounts; remove unused accounts.

## Frequently asked questions

**An account shows "Failed".**

The sign-in has expired, the password was changed or permissions were withdrawn. Reconnect the account in the flow designer (or create a new one) and select it in the affected flows.

**I don't see an account my colleague created.**

It is probably in their "Personal" area. Shared accounts belong in the "Team" area.

**Can I manage several customer tenants with one Microsoft account?**

No. An account applies to exactly one tenant. Create a separate account per customer.

**What permissions does a flow have with my Pro API key?**

The permissions of the API key at provider level – i.e. access to the data of all your customers. Keep the key safe accordingly.


---

# 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://hub.equipme.io/pro/automation/accounts.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.
