> For the complete documentation index, see [llms.txt](https://docs.archisketch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archisketch.com/guide/faq-en/partner-developer/sso.md). # SSO integration We’ve gathered questions about SSO integration for logging into Archisketch with a partner account. ## What is SSO? SSO (Single Sign-On) is a feature that integrates so you can log in to the Archisketch service with an account registered with a partner company. Users of the partner company can log in directly with their partner company account without a separate Archisketch account. ## Is SSO integration required? No, it is optional. 3D product registration and API integration are possible without SSO. SSO is needed when you want partner company users to use the Archisketch editor directly within the partner company's service. ## How do I start SSO integration? SSO integration requires developer work. For more details, please refer to [\[SSO Integration Guide\]](/guide/dev-kr/api-sdk/api-integration/sso-integration.md)or contact the person in charge. --- # 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://docs.archisketch.com/guide/faq-en/partner-developer/sso.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.