> 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/administration.md).

# Administration

The "Administration" area in Equipme Pro: supplier profile, users, roles and permissions, integrations, email notifications and customer portal settings at a glance.

**Path:** "Administration"

In the **"Administration"** area, you set up your provider company in Equipme Pro: company data, employees with access to Pro, their roles, interfaces, and the emails that Pro sends to your team and your customers.

| Menu item                                                               | Content                                                                                                                                 |
| ----------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| [**"Supplier Profile"**](/pro/administration/supplier-profile.md)       | Company data, bank details, Partner Connect profile, customer attributes                                                                |
| [**"User"**](/pro/administration/users.md)                              | Create employees with access to Pro, grant access, lock, remove                                                                         |
| [**"Roles and rights"**](/pro/administration/roles-and-permissions.md)  | Assign provider roles and roles in your customer portals                                                                                |
| [**"Integrations"**](/pro/administration/integrations.md)               | API key, product import from distributor catalogs, shipping service                                                                     |
| [**"Email notifications"**](/pro/administration/email-notifications.md) | Internal notifications, emails to your customers, sender settings                                                                       |
| **"Customer Portal Settings"**                                          | White label customer portal, legal texts, default settings for new customers – see [Customer portal](/pro/customers/customer-portal.md) |

## Who sees what?

| Role                    | Visible menu items                                                               |
| ----------------------- | -------------------------------------------------------------------------------- |
| **"Administrator"**     | all menu items                                                                   |
| **"Portfolio Manager"** | only **"Integrations"** (e.g. for the product import from a distributor catalog) |
| all other roles         | no access to "Administration"                                                    |

{% hint style="info" %}
With Lite access, the menu is limited to "Sales" → "Customers"; the "Administration" area does not exist there (see [Business models and licenses](/pro/getting-started/business-models.md)).
{% endhint %}

## Frequently asked questions

**Why don't I see "Administration"?**

You don't have the "Administrator" role. Ask an administrator of your company to assign you the role under [Roles and permissions](/pro/administration/roles-and-permissions.md).

**Where do I set the appearance of the customer portal?**

Under "Administration" → "Customer Portal Settings", described in [Customer portal](/pro/customers/customer-portal.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://hub.equipme.io/pro/administration.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.