> 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/customers.md). # Customer management at a glance Customer management in Equipme Pro: customer types (direct customer, end customer, partner, partner customer), the customer list with filters and actions, and customer permissions. **Path:** Sidebar → **"Sales"** → **"Customers"** Here you manage all companies you work with as a provider: the customers you run customer portals for, customers with their own equipme license, connected partners and customers that partners refer to you. From here you create new customers, connect customers via invitation ID, open customer portals and get to the customer details. ## Customer types The **"Type"** column shows what kind of customer it is. An info icon next to the type explains the relationship. | Type | Meaning | Edit and "Open customer portal" | | ---------------------- | --------------------------------------------------------------------------------------------------- | --------------------------------------- | | **"Direct customer"** | Hosted customer whose customer portal you run | ✓ | | **"End customer"** | "This is a standalone customer who has connected with you": customer with their own equipme license | – (only "Automatically confirm orders") | | **"Partner"** | "Partner to whom you can release your offers for referral." | – | | **"Partner customer"** | "This customer was referred to you by partner …" | – | For customers you don't manage, the "Portal" column shows a note instead of the icon: "You cannot edit this customer or access their portal because you do not manage them." Your own company is also in the list, with the suffix **"(Own organization)"**. Learn more under [Customer details](/pro/customers/customer-details.md#own-organization). How the customer types relate in business terms is described in [Business models and licenses](/pro/getting-started/business-models.md). ## The customer list ### Columns | Column | Content | | ------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------ | | **"Portal"** | Icon for opening the customer portal (direct customers only, not on small screens) | | "ID" | Internal number of the customer (hidden by default) | | **"Company name"** | Name of the customer | | **"Customer number"** | Your customer number for this customer | | **"Type"** | Customer type, see above | | Customer attributes | Up to three custom fields, if you have named and shown them in the [supplier profile](/pro/administration/supplier-profile.md) | | "Account manager", "Name (contact)", "Mail (contact)", "Phone (contact)" | Responsible user in your company and contact person at the customer (hidden by default) | | "Description" | Free text | | "Partner" | For partner customers: the referring partner | | **"Status of order authorization"** | "Authorized to order", "Not authorized to order" or "Waiting for order authorization" | | "Default currency" | The customer's primary currency | | **"Last order activity"** | Date of the last order | | "Global portfolio inherited" | Whether the customer sees your global portfolio | | "Active", "Created" | Status and creation date | | ⋮ | Actions, see below | ### Filter and export * Filter e.g. by **"Status of order authorization" = "Waiting for order authorization"** to see all open requests for order approval (see [Order approval](/pro/customers/customer-details.md#order-approval)). * Filter by **"Type"** to see e.g. only direct customers. * With **"Export"** you download the filtered list as an Excel file. General notes on search, filters and columns are under [The user interface](/pro/getting-started/user-interface.md#tables). ### Actions Above the table: * **"Add new customer"**: creates a Hosted customer. → [Create and invite customers](/pro/customers/create-and-invite-customers.md) * **"Enter invitation ID"**: connects you with a Standalone customer. → [Connecting Standalone customers](/pro/customers/create-and-invite-customers.md#connecting-standalone-customers) Per row (⋮ menu or right-click): | Action | Effect | | ------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **"Open customer portal"** | Opens the customer's portal in a new tab (direct customers only) | | **"Edit"** | Opens the [customer details](/pro/customers/customer-details.md) (direct customers only; requires the permission to edit customers) | | **"Show offers"** | Opens the customer details on the "Offers" tab | | **"Create offer"** → "Product" or "Service" | Creates a new service intended exclusively for this customer and opens it in the service portfolio. → [Offers and prices](/pro/portfolio/offers-and-pricing.md) | Clicking a row opens the [customer details](/pro/customers/customer-details.md). ## Who may do what? | Role | See customers | Create customers | Edit customers | Change portal settings | Delete customers | | ----------------- | ------------- | ---------------- | -------------- | ---------------------- | ---------------- | | "Administrator" | all | ✓ | ✓ | ✓ | ✓ | | "Account Manager" | all | ✓ | ✓ | – | – | | "Sales" | ✓ | ✓ | ✓ | ✓ | – | | "Reseller" | ✓ | ✓ | ✓ | – | – | * **"Account Manager"** users may access all customers and are automatically authorized for all customers. * **"Sales"** and **"Reseller"** users automatically get the customer role "Planner" for the customers they create themselves and can open their portal. They have no access to existing customers unless they are authorized there. * Changing the portal settings (e.g. order authorization, premium features) additionally requires the permission **"Manage customer settings"**. * Deleting a customer requires the delete permission for customers and administration rights. You define the exact permissions under [Roles and permissions](/pro/administration/roles-and-permissions.md). Which employees may access an individual customer is controlled in the [customer details](/pro/customers/customer-details.md#permitted-users). ## Frequently asked questions **Why can't I edit a customer?** Either they aren't a direct customer (you don't manage end customers, partners and partner customers yourself), or you lack the permission to edit customers. **How do I find customers waiting for their order approval?** Filter the "Status of order authorization" column by "Waiting for order authorization". You also receive an email if you have enabled the "Order authorization requested" notification. **Can I add my own columns to the customer list?** Yes, up to three customer attributes. You name them in the [supplier profile](/pro/administration/supplier-profile.md) and maintain the values per customer in the customer details. --- # 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/customers.md?ask=&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.