> 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/getting-started/user-interface.md). # The user interface Structure of the app: sidebar with "My workspace", header bar, user menu, language, tables with filters and views, error and info pages. ## Structure * **Sidebar (left):** the main menu for everything you do in equipme. At the top is the **"My workspace"** section with "My equipment" (your own equipment), "My Marketplace" (request new work equipment for yourself) and, where applicable, "My tickets". Below it follow, depending on your role, the menu items for the company or your area of responsibility (see [Roles and views](/dokumentation/getting-started/roles-and-views.md)). Groups such as "Company" or "Assets" can be expanded and collapsed; equipme remembers their state. Numbers next to "Approvals", "Order requests", "My tickets" and "Order processing" show open items. At the very bottom: **"Settings"** (administrators). * **Header bar (top):** menu button, logo, "Support", "Help", user menu and language. * **Content area:** the current page. On detail pages, the back arrow at the top left takes you to the previous page. On smartphones, the sidebar collapses; open it via the menu icon ☰. {% hint style="info" %} The header bar used to have a switch between "Company" and "Self-service". It has been removed: your personal areas and the management menus now share one sidebar. {% endhint %} ## The header bar | Element | Function | | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **☰ / back arrow** | Expand and collapse the sidebar, or go back | | **Logo** | Takes you to your start page, e.g. the "Dashboard" or "My equipment" | | **"Support"** | "Support request", "My tickets", "Ticket system" where applicable (agent view of [Equipme Operate](/dokumentation/operate.md)) and the support notice (only with Equipme Operate active or a support notice, see [Support requests and tickets](/dokumentation/self-service/tickets.md)) | | **"Help"** | Opens the AI assistant that answers questions based on this guide | | **User menu** | "My profile" where applicable (opens your employee page; only with a company role), "My account", "Info" (terms and conditions, privacy policy, legal notice, version), "Install PWA" where applicable, "Log out" | | **Language** | German, English, Spanish, French, Italian, Polish, Norwegian, Dutch | Your language selection is saved in the browser. Without your own selection, the company's preferred language applies. You receive notifications by email (see [Email notifications](/dokumentation/settings/email-notifications.md)) and as short pop-up messages in the app. ## Tables, filters and views All lists in equipme work the same way: * **Search:** search field above the table. * **Sort:** click the column header. * **Filter:** ⋮ menu or filter icon on the column. Depending on the column, there are value selections, yes/no, date ranges or conditions. * **Show and hide columns:** via the column icon at the top right. * **Group:** possible by a column in many tables. * **Save views:** via the **"Views"** icon at the top right → "+" → enter a name → save. This lets you save frequently used combinations of filters and columns, e.g. "Employees in offboarding" or "Devices with less than 3 months remaining term". To delete a view, hover over it and click the trash can. * **Export:** Many tables offer an Excel export of the current view. * **Multiple selection:** Select rows using the checkboxes; you'll then find bulk actions under **"Actions"**. * **Open in new tab:** right-click a row. ## Error and info pages | Display | Meaning | What to do? | | --------------------------------- | ----------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | | **"401 – Not authorized"** | You lack the role or license for this page. | Ask your administrator for the appropriate role | | **"403 – Access denied"** | You lack a specific permission, e.g. for the Marketplace in the self-service. | "Back" or contact your administrator | | **"404 – Page not found"** | The record no longer exists, e.g. after it was deleted. | Navigate again via the menu | | **"We'll be right back"** | Maintenance or brief unavailability | Wait a moment, "Back to start" | | **"Oops, something went wrong."** | The page is currently unavailable, e.g. because of a wrong portal address. | Check the address, try again later; contact [support](/dokumentation/help/support.md) if necessary | equipme tries to bridge brief connection problems automatically before an error message appears. --- # 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/getting-started/user-interface.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.