> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/account-administration/account-settings/invite-and-manage-users/control-user-sign-up-methods.md).

# ユーザー登録方法を管理する

ユーザーがアカウントに参加するためにどのようにサインアップできるかを設定し、ユーザーのサインアップ認可および認証方法を定義できます。

{% hint style="success" %}
**注**: 以下を持つユーザーのみ [アカウントのセキュリティ設定権限](/brand/ja/what-would-you-like-to-learn-about/account-administration/account-settings/invite-and-manage-users/understanding-user-management-as-a-brand.md) にアクセスできます *ユーザーサインアップ方法* セクション。
{% endhint %}

1. 上部ナビゲーションバーで、 ![](https://1458456015-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2F210dEQa93qyQgoJDkieL%2FUser%20profile.svg?alt=media\&token=f84c5b17-fae4-4a30-990a-9de5e57a150b) **\[ユーザープロフィール] → 設定**.
2. 左側の *一般* セクションで、 [**アカウントユーザー認証**](https://app.impact.com/secure/advertiser/accountSettings/account-security-settings-flow.ihtml).
3. で、 *ユーザーサインアップ方法* セクションで、ユーザーがアカウントに参加する際に使用する希望のサインアップ方法を選択してください。

{% tabs %}
{% tab title="シングルサインオン（SSO）" %}

1. 選択 ![](https://1458456015-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FwXho9QKP3e4iU4ZKUSJ5%2F167ebb8cc30303.svg?alt=media\&token=a046e9f0-63aa-46f6-8a35-f73973fd326c) **\[Checkbox]** **シングルサインオン（SSO）**.
2. 1つまたは複数のサインアップ方法を選択してください:
   * Apple
   * Google
     {% endtab %}

{% tab title="SAML" %}
を参照してください [SAMLシングルサインオンを有効にする](/brand/ja/what-would-you-like-to-learn-about/account-administration/account-settings/invite-and-manage-users/enable-saml-single-sign-on.md) この方法の使用方法の詳細については、

1. 選択 ![](https://1458456015-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FwXho9QKP3e4iU4ZKUSJ5%2F167ebb8cc30303.svg?alt=media\&token=a046e9f0-63aa-46f6-8a35-f73973fd326c) **\[Checkbox]** **SAML**.
2. 各申請者の横にある ![](https://1458456015-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-c2cb550b55c51ea1eeff0acbd6f437a03b621a2c%2F60d033ae8a04c14498d5229c3c0160ac05feea7f605dbd770741793c900469f0.svg?alt=media) **\[ドロップダウンメニュー]**&#x305D;の後、希望のオプションを選択してください:
   1. Impact
   2. AD FS
   3. Microsoft Entra ID
   4. Okta
   5. OneLogin

{% hint style="warning" %}
**重要**: 以下を使用してあなたのアカウントに参加したユーザー *SAML* 方法は次の方法に戻すことはできません *ユーザー名とパスワード* 方法。
{% endhint %}
{% endtab %}
{% endtabs %}

4. 選択 **保存**.


---

# 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://help.impact.com/brand/ja/what-would-you-like-to-learn-about/account-administration/account-settings/invite-and-manage-users/control-user-sign-up-methods.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.
