Update a Rule
Authorizations
Body
UpdatePolicyRuleRequestData
The Vendor role that users matching this rule should be assigned to. The role can only be changed if the rule is in a staged state. After a rule is activated, you will need to create a new rule or duplicate this rule to change the role assignment while it is in a staged state
^porol_[0-9a-hjkmnp-tv-z]{26}$"porol_01hq8xyzabc123def456ghi789"
Priority order between 1 and 99 for evaluating this rule among other rules in the same ruleset.
Lower numbers are evaluated first. Rules with the same priority are evaluated based on the greatest number of users matched (highest to lowest).
Rules for a specific user are always evaluated first (regardless of priority) before other rules to ensure that user-specific elevated roles take precedence.
If not set, the default priority is 42 (obviously...)
1 <= x <= 9942
Response
PolicyRuleDetailedResponseData
Users will be automatically deprecated if they no longer qualify for at least one rule in the ruleset.
The expires_after_days value determines how many days after they no longer qualify that they still
have access for a graceful transition period when users change job roles.
The value is inherited from the Workspace > Dimension (for Directory Attributes) > Ruleset and can be
overridden at any level to provide shorter revoke time controls when needed.
If the value is 0, this skips the grace period and revokes access immediately after expires_at.
By default, users have perpetual access (as Policy Users) as long as their attributes continue to match
the conditions for this rule. If this rule is designed for just-in-time or short term access, you can
set the expires_at date for all conditional users to be deprecated at that time.
You can use expires_at and expires_after_days=0 together to revoke access immediately
Priority order between 1 and 99 for evaluating this rule among other rules in the same ruleset.
Lower numbers are evaluated first. Rules with the same priority are evaluated based on the greatest number of users matched (highest to lowest).
Rules for a specific user are always evaluated first (regardless of priority) before other rules to ensure that user-specific elevated roles take precedence.
If not set, the default priority is 42 (obviously...)
42