This is not a valid development step. A Quicklink is configured as an IdentityIQ object that exposes an action to users through the UI and can be configured to launch a workflow. The workflow does not contain or "host" the Quicklink object. The relationship is the other way around: the Quicklink references the workflow it should launch. To restrict the Quicklink to managers only, the engineer should configure visibility, population, capability, or dynamic eligibility logic so only manager identities can see or execute it. Then the Quicklink configuration should identify the workflow to invoke and pass any required arguments into that workflow. Placing a Quicklink object "on" the workflow is not how IdentityIQ Quicklink architecture works.
The proposed solution confuses the launching object with the launched process. References/topics: IdentityIQ Engineer - Quicklink object, workflow launch configuration, manager-only visibility, population rules, workflow arguments.