Available automation components for authentication policies
Automation rules are made up of three key components. Build automation rules using triggers, conditions and actions.
Triggers – Start the rule when a specific event occurs.
Conditions – Specify criteria that must be met for the rule to continue. (Optional)
Actions – Perform tasks when the rule satisfies the criteria.
Available triggers
Trigger group | Trigger | Description |
---|---|---|
Group | User added to a group | Rule triggers when you add a user to a group. |
User removed from a group | Rule triggers when you remove a user from a group. | |
Identity provider | Users removed from an identity provider directory | Rule triggers when users are removed from an identity provider directory. |
Users synced to an identity provider directory | Rule triggers when your identity provider syncs users to an identity provider directory. | |
Account | User profile updated
| Rule triggers when you update any of the following user profile details:
|
User is a managed account | Rule triggers when a user becomes a managed account. This trigger needs no additional configuration. |
Available conditions
Conditions | Criteria | Description |
---|---|---|
User authentication policy |
| Checks whether the authentication policy meets a certain criteria. |
User domain |
| Checks whether a user domain meets a certain criteria. |
User group |
| Checks whether user group membership meets a certain criteria. |
User identity provider |
| Checks whether the user identity provider meets a certain criteria. |
User profile information | For email, Job title, Location:
For timezone:
| Checks whether the user profile information meets a certain criteria. |
Available actions
Action | Description |
---|---|
Assign user to authentication policy | The authentication policy is assigned when your rule runs successfully. |
Was this helpful?