> For the complete documentation index, see [llms.txt](https://docs.idlayr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.idlayr.com/enterprise-portal/sign-in.md). # Sign in The Enterprise Portal mainly uses **Single Sign-On (SSO) via SAML** (powered by WorkOS) as its authentication. Your team signs in through your organisation's identity provider — Okta, Azure AD, Google Workspace, OneLogin, JumpCloud, or any other SAML 2.0 IdP (more details: ). There's no password to manage on the IDlayr side. There are some exceptions when we can enable per user login, these cases are discussed separately with the IDlayr team. ## Why SSO is prefered Customer-management surfaces inevitably need to be access-controlled at the organisation level: who joined, who left, who has what role. SAML SSO is the only authentication model that lets your existing identity team manage that lifecycle without IDlayr having to mirror it. ## Setting it up SSO setup is a one-time configuration done in coordination with your IDlayr account team. The typical flow: 1. **IDlayr prepares** organization and workspace setup in the portal. 2. **You identify a designated contact** responsible for identity management, SSO/SAML configuration, and user access control. 3. This person receives **the invitation** from IDlayr team to configure IDlayr Portal as a SAML application in your IdP. 4. **Your contact completes the connection** on the Portal side. 5. **Your team can sign in** at the Portal URL provided during onboarding by clicking "Sign in with SSO" and entering your organisation's identifier. Specific IdP-by-IdP setup instructions (Okta, Azure AD, Google Workspace, etc.) — contact your IDlayr account team. We share IdP-specific configuration guides as needed during onboarding. ## Domain matching Your SSO connection is tied to one or more **email domains** belonging to your organisation. When a user with `@your-company.com` arrives at the Portal sign-in screen, the Portal routes them through your IdP automatically. ## Who can sign in Anyone whose IdP account exists in your IDlayr-linked SAML connection can sign in to the Portal. The Portal **does not** auto-provision arbitrary IdP accounts as Portal users with elevated roles — see [Users and roles](/enterprise-portal/users-and-roles.md) for how role assignment works. ## What if SSO is down? If your IdP is temporarily unavailable, contact your IDlayr account team. There's no backup password-based sign-in by design; emergency access is handled out-of-band. ## What's next * [**Projects**](/enterprise-portal/projects.md) — once signed in, create your first project. * [**Users and roles**](/enterprise-portal/users-and-roles.md) — set who on your team has access to what. --- # 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://docs.idlayr.com/enterprise-portal/sign-in.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.