I have a requirement where the end user will select a category, and based on the selected category, the user should automatically receive default group access.
For example, the categories could be:
Admin
Service Desk
Customer View
Once the user selects any of these categories, the system should automatically assign the corresponding default groups.
I would like to implement this using a QuickLink, following the same approval process that we have already configured in the system.
I want to understand
After the user selects a category in the QuickLink, which workflow should be triggered?
How can we provision all the default groups automatically based on the selected category?
Can someone please guide me on the best way to implement this?
I would recommend to create your custom workflow in which handle the user selection part through form and then based on the user selection build a plan. Then call the main workflow you have configured in lifecycle manager for “Request Access”. Make sure you pass all the required arguments needed for the main workflow.
Are these “categories” roles? Could you model these categories as different business roles? If so, then can use your OOTB Manage User Access process to handle this
Otherwise if you need to present these categories in a different interface, you’d want to use a custom Quicklink / Form / Workflow design and your workflow would call the Request Access workflow you have configured with your input arguments.
You can create a custom quicklink triggering a custom workflow displaying a form with a dropdown containing the categories, and then you can pass the selected categories to the next step, create approvals in a step and then provision the default access based on selected category in a rule.
@AMANSINGH12 You can achieve this via custom workflow using a quicklink + form and based on category selection, you can build your plan to provision the groups. You can store the mapping in the custom object like for which category, what groups needs to be provisioned. Then pass the plan to your LCM Workflow.
As you have implemented custom quicklink, you can trigger custom workflow by passing necessary workflow arguments captured in Form. In your workflow steps, Provisioning Plan can be created which is again passed to OOTB LCM Provisioning workflow or similar workflow which is used for all provisioning requests in your organization. This can ensure logging Audits, tracking though Access request and Object locking mechanism.
Hi @AMANSINGH12 — great answers already in this thread. I’d strongly second Keith’s suggestion: the cleanest IIQ-native approach is to model each category (Admin, Service Desk, Customer View) as a Business Role, with the corresponding default groups assigned as required IT Roles underneath. Users simply request the Business Role via the standard LCM Request Access page — no custom QuickLink or workflow needed — and your existing approval process fires automatically.
