您的组织可以使用以下模式，以便在 Automation Cloud 中创建用户：
- The invitation-based model, available as the All available methods option, which is the default model set for any new organization. The organization administrator manually adds the email addresses of users to send an email invitation to join the Automation Cloud organization. In turn, users create a UiPath account as they accept the invitation, which is the identity they use to sign in to Automation Cloud.
This model is compatible with the other models. If you choose to use any of the other models, you can continue to create users in Automation Cloud by invitation.
- The Azure Active Directory model: If you have a Microsoft Azure or Office 365 subscription, you can integrate Azure with Automation Cloud to use your existing users and groups from Azure Active Directory within Automation Cloud.
- The SAML model lets you integrate Automation Cloud with your chosen identity provider (IdP). This lets your users connect to Automation Cloud with single sign-on (SSO) using the accounts that are already registered with your IdP.
用户身份验证是根据组织目录在 Automation Cloud 中完成，更确切地说，是通过 Cloud Portal 来验证用户的身份。在这里，根据通过角色和组分配的用户权限，用户只用一组凭据就可以访问您所有的 UiPath Cloud 服务。
In the invitation-based model, identity management is performed on a user reference in the organization directory, while users remain in control of their accounts. But if integrated with Azure Active Directory (Azure AD), it's as simple as looking at the contents of your tenant directory in Azure AD, depicted below with an orange arrow.
You can read more about each model in the following sections.
- Go to Admin > organization > Security.
Without third-party integrations, you can use the local account options which rely on automation Cloud for managing accounts. If you have set up an integration with an external identity provider, use the options for directory integrations.
The invitation-based model (All available methods option in the image above) is set by default for any new organization.
If you are switching from a directory model back to a local account model, there are a few things you must do before changing the authentication model:
Updated a day ago