> 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-jp/partner-developer/sso.md).

# SSO連携

パートナー企業アカウントでArchisketchにログインするSSO連携に関する質問を集めました。

## SSOとは何ですか？

SSO（Single Sign-On）は、パートナー企業に登録されたアカウントでArchisketchサービスにログインできるように連携する機能です。パートナー企業のユーザーは、別途Archisketchアカウントを作成しなくても、パートナー企業のアカウントでそのままログインできます。

## SSO連携は必須ですか？

いいえ、任意です。3D商品登録およびAPI連携はSSOなしでも可能です。SSOは、パートナー企業のユーザーがArchisketchエディターをパートナー企業のサービス内で直接使用できるようにする場合に必要です。

## SSO連携を始めるにはどうすればよいですか？

SSO連携には開発者の対応が必要です。詳細は [\[SSO連携ガイド\]](https://docs.archisketch.com/guide/dev-kr/api-sdk/api-integration/sso-integration.md)をご参照いただくか、担当者までお問い合わせください。


---

# 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-jp/partner-developer/sso.md?ask=<question>&goal=<user_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.
