> 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/customer-portal.md). # Customer portal (white label) Set up the white-label customer portal: theme (logo, favicon, colors), default module settings, marketplace offers, legal texts, order settings, custom links, own portal address. **Path:** Sidebar → **"Administration"** → **"Customer Portal Settings"** Here you set up the customer portal that your Hosted customers (direct customers) use. With your own logo, your own colors, your legal texts and your portal address, you offer the portal as **your own product**. You also define which features new customers start with. **Who may do this?** Users with administration rights, usually the role "Administrator". The page has six tabs: | Tab | Content | | --------------------------------------------------------- | --------------------------------------------------------------------------------------- | | [**"Theme"**](#theme) | Logo, favicon, app title, colors | | [**"Default module settings"**](#default-module-settings) | Modules and global portfolio for new customers, system products, Workplace as a Service | | [**"Support note"**](#support-note) | Note text in your customers' support area | | [**"Legal notice"**](#legal-notice) | Links to privacy notice, legal notice and terms and conditions | | [**"Order settings"**](#order-settings) | Phone number in the delivery address, text of the order button, approval notes | | [**"Custom links"**](#custom-links) | Your own links in the customer portal menu | These settings apply to **all Hosted customers**. For individual customers, you adjust modules and order permissions in the [customer details](/pro/customers/customer-details.md#portal-settings); a customer gets a different branding through their own [customer theme](#custom-theme-for-individual-customers). ## Theme The theme defines the look of Equipme Pro **and** of all customer portals whose customers don't have their own customer theme. | Section | Settings | | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **"Primary color"** | Color of the greeting text, the navigation aid and the badges. It also determines the color of the toolbar and the buttons, unless you set your own colors for them. | | **"Favicon & title"** | Icon in the browser tab (PNG, square, at least 512 × 512 px) and **"App title"** (required), which appears in the browser tab. With "Reset" you restore the default icon. | | **"Logos & Toolbar"** | Two logos: one that is clearly visible **on a white background** (mainly for emails and documents), and one that is easy to read **on your primary color** (for your customers' interface and toolbar). Minimum width 400 px each. Optionally a **"Toolbar color gradient enabled"** with "Degree", "Start color", "Transition color" and "Final color" including percentages; "Preview" shows the result. | | **"Button colors"** | With **"Button theming active"** you set your own colors for the states "Default", "Hover", "Active" and "Disabled", each with fill and text color, plus a text color for disabled buttons with a border. Without button theming, the primary color applies. | 1. Make your changes. 2. Click **"Save"** and confirm: "The changed theme will be applied to all users and customers who do not have their own custom theme." With **"Delete"** you remove your theme again. {% hint style="info" %} **Dark mode:** If you use Equipme Pro in dark mode, note that the theme doesn't distinguish between light and dark. Your customers always use the portal in light mode. Choose your colors accordingly. {% endhint %} ### Custom theme for individual customers A customer can get their own branding, e.g. with their company logo: * **During creation:** in the wizard via "Customize your customer portal" (see [Create and invite customers](/pro/customers/create-and-invite-customers.md#creating-hosted-customers)). * **Later:** Open the customer's portal ("Open customer portal") and there the theme settings. Without a customer theme, the page shows a note that the customer sees your provider theme. With **"Create customer theme"** you create a separate theme for this customer based on your provider theme and adjust it. {% hint style="warning" %} If a customer has their own customer theme, **later changes to your provider theme are not applied**. You then maintain logo, favicon and colors in this customer's portal. If you delete the customer theme there, the customer sees your provider theme again. {% endhint %} ## Default module settings Here you set which modules **new customers** get by default. The settings apply to customers you create or who register via your portal address. You adjust them per customer later in the [customer details](/pro/customers/customer-details.md#portal-settings). | Setting | Meaning | Default | | ----------------------------- | ---------------------------------------------------- | -------- | | **"Enable invoice view"** | New customers see the "Invoices" menu item. | active | | **"Enable inventory module"** | New customers can use the internal inventory module. | inactive | Click **"Save"** to apply your selection. {% hint style="info" %} The **"Enable ticket system"** setting does not control the Equipme Operate ticket system. equipme activates Equipme Operate for your customers, see [Ticket system (Equipme Operate)](/pro/operations/tickets.md#activating-equipme-operate-for-a-customer). {% endhint %} ### Global marketplace offers With **"Inherit global portfolio"** you define whether new customers see your global portfolio in the marketplace right after signing in. If the switch is off, new customers only see the services you release to them specifically. The change is saved immediately and only applies to new customers. How to release offers is described under [Offers and prices](/pro/portfolio/offers-and-pricing.md). ### System products System products are booked automatically when a new **customer** is created, or when a **location** or an **employee** is created for a customer. You use them, for example, to map a one-time fee per employee onboarding or a monthly base fee per customer. * **Default (switch off):** The system product is ordered and activated automatically. Neither you nor the customer need to do anything; no order is created that someone has to confirm or process. If a price is set, it is still charged; this is how the fees arise. * **"Approval required" (switch on):** The customer has to order the system product manually, and you process the order before it becomes active. The switch applies to all system products and all your customers. ### Workplace as a Service "Workplace as a Service" maps digital workplace systems: the workplace product is booked to employees and bundles software licenses and options around the digital workplace. If it isn't active for a customer, the workplace management features (e.g. activation for an employee, provisioning via templates) aren't available to them. * **"Always enable for new customers"**: new customers get Workplace as a Service automatically. * In the customer table, you choose which **existing customers** use Workplace as a Service. * Click **"Save"**. ## Support note An active support note appears for your customers in the "Support request" dialog and in the support menu in the header. Use it, for example, for a phone number, service hours or notes on reporting incidents. 1. Choose the input language. 2. Click **"Create support note"** and enter the text in the editor. Maintain the text for every language your customers use. For languages without text, "No support note defined for this language" appears. 3. Save and turn the note on or off with **"Active"**. With "Delete" you remove the note. ## Legal notice Links to the privacy policy, legal notice and general terms and conditions. 1. Choose the language. 2. Enter the addresses (starting with `https://`): **"Privacy notice"**, **"Legal notice"**, **"General Terms and Conditions"**. 3. Repeat this for other languages and click **"Save"**. **What your customer sees:** In the user menu of their portal under "Info", the entries for terms and conditions, privacy and legal notice open the links you stored, in the user's language. If a link is missing in their language, the portal uses the link of another stored language. If the privacy notice or legal notice is missing entirely, equipme's are shown. The same links also apply in Equipme Pro. ## Order settings ### Phone number in the delivery address With **"Phone number required in the delivery address"** you prevent orders whose delivery address contains no phone number, e.g. because your shipping provider requires one. Click **"Save"**. ### Text of the order button Here you adjust the text of the order button on your customers' approval page. Click **"Edit"**, enter the text for German and English, and click **"Save"**. Without your own text, the default text applies (marked "(default)" in the field). ### Approval notes Your customers see approval notes on the approval page before they order, e.g. a link to your terms and conditions. You can create up to **three** notes. 1. Click **"New entry"** and enter the text in the editor (per language). 2. Define: * **"Position"**: where on the approval page the note preferably appears, * **"Confirmation required"**: the customer must confirm the note before they can order, * **"Active"**: the note is visible to customers. 3. Click **"Save"**. ## Custom links Custom links appear in the customer portal menu in an additional menu group, e.g. for your self-service portal, forms or documentation. 1. Click **"Edit"** next to **"Name of the menu group"** and enter the name per language (max. 50 characters). Without your own name, the group is called "Further resources". 2. Click the **+** to create a link (up to 20 links): display name per language and URL. 3. Optionally restrict for which **"Customers"** and which **"Roles"** the link is visible. 4. Click **"Save"**. You change the order via drag and drop. ## Your own portal address equipme sets up a dedicated domain for your customer portal (e.g. `portal.your-company.com`) for you. To get one, contact [support](/pro/help/support.md). Via this address * your customers sign in and see your branding, * new customers can register themselves and are automatically created as your direct customers (see [Registration via the portal address](/pro/customers/create-and-invite-customers.md#registration-via-the-portal-address)). ## Frequently asked questions **My customer still sees the old logo.** Check whether the customer has their own customer theme. If so, changes to your provider theme don't take effect. Delete the customer theme in the customer's portal or adjust it there. If that doesn't solve the problem, reload the page so the browser loads the new logo. **Do the default module settings apply retroactively?** No, only to new customers. You adjust existing customers in the [customer details](/pro/customers/customer-details.md#portal-settings). **Can I store separate terms and conditions for each customer?** No. The legal notice applies to all your customers. **Can my customers edit the support note?** No. The support note comes from you. Your customers only see it. **Why is "Phone number required in the delivery address" grayed out?** The setting is currently loading or saving. Wait a moment and try again. --- # 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/customer-portal.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.