Your parameters, not the agent's logic
This is where your organization tunes how the certified agent behaves for you — allowed intake channels, default access and activation, and validation strictness. The underlying decision logic was reviewed and certified by a domain expert and cannot be changed here.
Trigger sources
Which intake channels this tenant is allowed to use.
Manual entry
Admins can key in a new user request by hand.
Automated feed (SuccessFactors / HR)
Requests arrive as an event payload from the HR system of record.
Default access assignment
Pre-selected branch in the access assignment step of the intake flow.
Block Administrator assignment
Prevents the agent from granting the privileged IAS Administrator role.
Activation & validation policy
Defaults applied to every new request for this tenant.
Default activation behavior
Whether the activation email goes out as soon as the user is created.
Require corporate/employee ID
Adds a hard validation rule for the employee ID field.