> 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/documentation/administration/portal-settings/direct-login-with-single-sign-on.md). # Direct Login with Single Sign On Direct SSO login links send users straight into the selected single sign-on flow. This is useful when an organization already uses Microsoft SSO and users should not have to choose the login method manually first. Instead of opening equipme and selecting the SSO option, the link already points to the correct provider. ### Link structure For Microsoft SSO, the standard equipme link is: **`https://app.equipme.io/sso?provider=microsoft`** If your equipme environment uses a custom domain, use the same path with your own domain: **`https://your-domain.com/sso?provider=microsoft`** Only the domain changes. The SSO path stays the same. ### When to use direct SSO links Direct SSO links are useful whenever users enter equipme from outside the application. This can be an internal help page, an intranet, onboarding instructions, customer communication, documentation or another system that links users back to equipme. Instead of sending users to a general login page, you can guide them directly into the login flow that matches their company setup. ### Example A company uses Microsoft as its single sign-on provider and has its own equipme portal domain. The direct SSO login link would follow this structure: **`https://your-domain.com/sso?provider=microsoft`** When users open the link, they are sent directly into the Microsoft SSO login flow. ### A clearer login path Direct SSO login links remove one step from the login process. Users do not need to decide which login option to select, because the provider is already defined in the link. This makes the entry into equipme clearer, especially when links are used in a specific context such as internal documentation, customer communication or connected systems. --- # 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/documentation/administration/portal-settings/direct-login-with-single-sign-on.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.