> 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/sign-in-and-registration.md). # Sign-in and registration Signing in, single sign-on, registering a new company, changing your password and common sign-in problems. ## Signing in 1. Open your equipme portal's address in your browser. 2. Without an active session, you are automatically redirected to the sign-in page. 3. Sign in with your username/email and password, or choose sign-in with Microsoft (if single sign-on is set up). 4. After signing in, you land on the page you originally wanted to open, otherwise on your start page (see below). Your session is automatically extended in the background. If that is no longer possible, the page reloads and you are redirected to sign in again. ### Single sign-on with Microsoft If Microsoft Entra ID is set up for your company, you sign in with your company account. The **direct SSO link** lets you skip the sign-in screen: ``` https:///sso?provider=microsoft ``` Administrators can place this link in the intranet or in invitation emails, for example. If you are already signed in, it takes you directly to the start page. The setup is described in [Integrations and single sign-on](/dokumentation/settings/integrations-and-sso.md). If synchronization with Microsoft Entra ID is active, equipme takes over your profile data (e.g. groups and supervisor) from Microsoft when you sign in. ### Changing your password and sign-in details Open the **user menu** (top right) → **"My account"**. Account management opens in a new tab. There you change your password and sign-in details. If you sign in via Microsoft SSO, you change your password at Microsoft. ## Start page after signing in equipme selects the start page automatically based on your role: | Role | Start page | | --------------------------------------------------------------------- | ------------------------------------------------ | | Administrator, purchaser, planner, controller | The company **"Dashboard"** | | Supervisor, location manager, business owner (without a company role) | **"Dashboard"** ("My organization" menu) | | Portfolio Manager responsible for an organizational unit | **Service portfolio** | | Fulfillment staff responsible for an organizational unit | **"Order processing"** | | Employee without any other role | **"My equipment"** in the "My workspace" section | | No permission | **"Not authorized"** page | Learn more under [Roles and views](/dokumentation/getting-started/roles-and-views.md). ## Registering a new company If you sign in for the first time and don't belong to a company in equipme yet, registration opens automatically. Which variant you see depends on the portal address you come from. This determines the [operating model](/dokumentation/getting-started/operating-models.md). {% hint style="info" %} If you were invited by your company, you don't need to register. Your administrator has already created you as an employee. Use the link from the invitation email. {% endhint %} You need a **business email address** to register. Addresses from free email providers and disposable addresses are rejected; this applies to both variants. ### Registering directly with equipme (Standalone) The "Almost done—Complete setup for Equipme" wizard guides you through the setup in three steps. With **"Continue later"**, you interrupt the setup and are logged out. 1. **"Customize your workspace"** * Select the **"Portal language"**. * Enter the **"Company domain"** (e.g. `deinefirma.de`) and click **"Find branding"**. equipme looks for the company's publicly available logo, colors and favicon and shows a preview of the workspace. * With **"Skip"**, you leave out this step. You can change everything later under [Theme](/dokumentation/settings/theme.md). 2. **"Set your location"**: "Company name", "Country", street, house number, postal code and city. Depending on the country, additional fields are added. 3. **"Add team members"**: optionally up to five email addresses of colleagues. Finish with **"Done"**. **Result:** * Your company is created. Company and billing address are initially identical. * A first location with the company name is created. * You become the first employee with the roles **Administrator**, **User** and **Portfolio Manager**. * Invited colleagues receive an invitation email and also become **administrators**. Adjust the roles afterwards as needed under [Roles and rights](/dokumentation/settings/roles-and-permissions.md). * Standalone companies start with a **free trial period**. A banner shows the remaining days. When it expires, navigation is locked until a plan is booked ("Contact us"). ### Registering via a provider's portal address (Hosted) If you come via the address of your IT service provider or provider, you see the form "Register now as a customer at *provider name*": * Fill in "Company", "First name", "Last name". "Username" and "Email" come from your sign-in account. * Click **"Register"**. Your company is created as a customer of this provider and you become administrator. The provider is notified. **You can only order once the provider has granted ordering permission** (see [Operating models](/dokumentation/getting-started/operating-models.md#ordering-permission-for-hosted-customers)). If registration is not enabled for a portal address, "Your user has not yet been activated. Please contact your administrator." appears. ## Logging out User menu → **"Log out"**. ## Installing the app as an application If your browser supports it, you'll find **"Install PWA"** in the user menu. equipme is then installed as a standalone app on your desktop or home screen. ## Sign-in problems | Message | Cause and solution | | ------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | "Login not allowed" – "Your account is currently not activated …" | Your user account is deactivated or your employee status does not allow sign-in. Contact your administrator. | | "Your registration has been rejected!" – "… not enabled for automatic Microsoft Entra ID registration" | Your Microsoft account is not yet linked to an employee in equipme and automatic registration is not enabled. Your administrator needs to create or invite you. | | "Your user has not yet been activated …" | You are not yet assigned to a company and registration is not possible via this address. Use your company's invitation link. | | Registration fails | Check that you are using a business email address. Private addresses from free providers and disposable addresses are not allowed. | | "This email is already registered" | An account already exists for this email address. Sign in or reset your password. | | "401 – Not authorized" page | You don't have a role that allows a start page. Your administrator needs to assign you a role. | Other error pages are explained in [The user interface](/dokumentation/getting-started/user-interface.md#error-and-info-pages). --- # 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/sign-in-and-registration.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.