multi-router.aidocs

User Provisioning (SCIM)

RulesEnterprise

Granting access from directory groups and attributes.

A rule grants access to the people who match it. Each rule has one condition, a pushed group or an attribute value, and a bundle of access to grant, the same bundle an invitation sets: an account role, roles in organizations, and Portal access with a tools policy. Rules are managed on the Rules tab of the People page.

Conditions

A rule's condition is one of these:

ConditionMatches
GroupMembers of a group the identity provider pushes, such as Engineering.
DepartmentPeople whose department equals a value.
DivisionPeople whose division equals a value.
OrganizationPeople whose organization attribute equals a value.
Cost centerPeople whose cost center equals a value.
TitlePeople whose title equals a value.
User typePeople whose user type equals a value.

Attribute values match regardless of letter case and surrounding spaces. Group conditions list the groups the identity provider has pushed; No pushed groups found means group push is still to be turned on there. An account holds up to 100 rules.

What a rule grants

A rule's bundle can grant:

GrantValues
Account roleAdmin, Member or none.
Organization roleAdmin, Member or none, for each organization.
Portal accessAccess to the Portal with a tools policy, which decides the tools the person can set up.

A person matched by several rules receives every rule's grants together, up to five rules. A person matched by more than five rules appears in Review under Rules that could not run, and the rules apply once they are narrowed. Rule access for an invited person starts when they accept their invitation, and rules apply to people whose directory record is active. Portal access lets the person set up tools such as Claude Code from the Portal, which then creates their router and API key. See Self-Service Provisioning.

Approvals

When a matching rule grants the account Admin role, all of the person's rule access waits for an account admin's approval, whatever the arrival setting. With Require admin approval, every grant waits. Approvals appear in Review under Waiting for your approval, and a grant that changes the tools policy of existing access appears under Policy changes to review. An account admin's Apply to all counts as approval. See Review and Notifications.

Applying a rule to existing people

A new or changed rule applies to people as the directory next updates them, following the arrival setting. To apply it to everyone who already matches, turn the rule on, preview it, and select Apply to all. Apply to all handles rules that match up to 250 people; a rule that matches more is split into narrower rules, such as by group, and each is applied.

Turning off and deleting rules

The two ways to retire a rule treat existing access differently:

ActionExisting access
Turn the rule offStays. The rule stops granting to new matches.
Delete the ruleGoes to Review, where an admin keeps or removes each grant.

Rule and admin grants

Each grant records where it came from: a rule or an admin. A rule changes only its own grants, and an admin changes a rule's grant by changing the rule. Keep access in Review converts a rule's grant into an admin grant that stays when the rule no longer matches.

Example

A company pushes an Okta group named Engineering and creates a rule: Group is Engineering, with organization role Member in Engineering and Portal access with the tools policy Claude Code for engineers. With Apply rules automatically, each engineer Okta pushes becomes a member of the Engineering organization and can set up Claude Code from the Portal on their first sign-in. When someone leaves the Engineering group, their access goes to Review for an admin to keep or remove.

Other DirectoriesReview and Notifications
Was this helpful?