> 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/release-updates/2026/september.md). # September ### **Update 18.09.2026 Release** ### Creating a new customer: one guided flow, all settings in one place

Adding a customer used to mean two jobs. First you created the customer, then you went back into the customer details to switch on everything the wizard didn't cover. Roughly half of the settings were missing from the flow. That's fixed. The customer creation wizard has been rebuilt from the ground up, and it now contains every setting you can see in the customer detail view — branding, modules, premium features, report configuration, currency. You can set up a complete, ready-to-work customer without leaving the flow once. Here's what the new wizard looks like.

### Where to start You have two entry points, both in the provider portal: * **Sales → Customers → Add new customer** * The **Add** menu in the top right → **New customer**

Both open the same wizard. If a customer already has an invitation ID, **Enter invitation ID** on the Customers page is still the right route. The wizard guides you through four steps. The progress panel on the right shows where you are and what's still ahead. ### Step 1 — Customize your workspace You start with the customer's look and feel — and this is the part that saves you the most time.

Pick the **company language**, then enter the **company domain** and select **Find branding**. Equipme reads the customer's corporate design straight from their website. It's the same branding service you already know from the registration flow. What comes back: * **Brand assets** — the company logo and the favicon, pulled from the domain. * **Brand colors** — the colours found on the site, shown as swatches. Select the one you want as the customer's primary colour. * **Preview of your workspace** — a live preview so you can check the result before you continue. No asset hunting, no colour codes to chase down. Type the domain, check the preview, move on. The customer's first login already looks like their own company.

Two things worth knowing: * **Skip** is always available. If you don't have the domain yet, or the customer wants to supply their own assets later, move on without it. * Nothing here is final. Every setting from this step can be changed later in the workspace settings. ### Step 2 — Set your location Next you define the customer's location. This is the address the workspace is set up around, and it becomes the basis for everything that follows — deliveries, employee assignments, and the customer's own location structure.

### Step 3 — Portal settings This is the step that changed the most. Everything that decides how the customer works with the platform now sits here, in one scrollable panel.

**Modules and access** * **Supplier warehouse active** — the customer can order services from your customer-specific warehouse and return them to it. * **Enable ticket system** — gives the customer access to the ticket system. **Premium features** * **Enable HR sync** — the customer can synchronise their organisational structure automatically from their HR or identity system. Note that this feature comes with additional license costs. * **Enable internal inventory module** — the customer can record their own internal inventory assets and offer their own internal services through the marketplace. * **Enable billing module** — creates monthly invoices for the customer. With the module switched off, no invoices are created and the billing module stays hidden. **Report configuration** * **Invoice** — the customer can download the PDF invoice in the billing module and, where available, receive it by email. * **Investment request** — the customer can download the investment request in the approvals section. * **Currency** — the customer's default currency, selected directly in the wizard. Euro is preset. Take a moment on this step. These toggles define what the customer sees when they log in for the first time, and getting them right here saves a round trip through the customer settings later. ### Step 4 — Add your first employee (optional) The last step lets you create the customer's first employee right away: first name, last name, email.

Switch on **Send invitation to users via email** and the employee receives their invitation immediately — the customer is live with a working user from day one. This step is optional. Leave the fields empty and select **Done** if you'd rather hand the workspace over and let the customer add their people themselves. ### What this means for you * **One pass instead of two.** No more creating a customer and then reopening it to complete the setup. * **Everything the detail view offers.** The wizard and the customer detail view now cover the same settings. * **A branded workspace from the start.** Branding is defined before the customer ever logs in. * **A tighter layout.** The flow is more compact and easier to scan, without hiding anything. Nothing has been removed and no behaviour has changed — this is the same customer setup you know, just complete and in one place. If something in the new flow feels off or you'd order the steps differently, let us know. We're actively watching feedback on this one. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://hub.equipme.io/release-updates/2026/september.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.