> 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/dokumentation/settings/portal-settings.md).

# Portal settings

Portal settings: preferred language, default currency, confirmation of receipt, phone number requirement, self-service delivery addresses and additional table columns.

**Path:** Settings → **"Portal settings"**

## "General"

| Setting                                             | Effect                                                                                                                                                                                                                                                                      |
| --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **"Preferred language"**                            | The company's language: default language for new sessions and language of emails (German or English; other languages receive English emails). Each user can switch the interface via the flag in the header.                                                                |
| **Default currency**                                | Currency of all prices and costs. **Can only be changed as long as no active assets exist.**                                                                                                                                                                                |
| **"Confirmation of receipt"**                       | Employees or responsible managers confirm receipt of new services. Open confirmations appear in the dashboard, in the profile and in the inventory. You set up the related email and reminders under [Email notifications](/dokumentation/settings/email-notifications.md). |
| **"Phone number required in the delivery address"** | Orders are only possible if the delivery address has a phone number (important for some shipping providers).                                                                                                                                                                |

Apply with **"Save"**.

## "Self-Service Configuration"

Under **"Delivery address"** you define which delivery addresses employees may choose in self-service:

* **"Work location"**: address of the assigned location,
* **"Home office"**,
* **"Custom address"**: a freely entered address (country, street, postal code, city, additional info, phone).

At least one option must be active. The selection appears when an employee requests a service.

## "Additional table columns"

Here you make **service features** (e.g. serial number, IMEI, service tag) available as separate columns in the **inventory**.

1. Via **"Add a column"**, enter a **"Column Name"** and the **"Source field"**. The name must exactly match the feature name maintained on the services (column "Asset Features").
2. Save.

The column is available to all users; each user shows it in the table as needed. It is included in the Excel export. Removing a column is permanent; the features on the services are retained.


---

# 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/dokumentation/settings/portal-settings.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.