Provisioning is the process of changing user access to systems and data in your enterprise. It can be initiated by users through actions such as access requests, certifications, or manager requests, or through automated configurations. Automated configurations include role assignments and lifecycle states that keep user access aligned with their business requirements.
I don’t see any mention here about the Source “features” attribute and setting the PROVISIONING flag on it, or checking for the PROVISIONING flag before configuring provisioning.
It would also be great to include a section on how to turn OFF provisioning for a source (Many clients want to do certification only with the source, and have a manual process for handling the revoking of access. ) It would also be good to note what happens when Provisioning is disable on a source with items such as certification. I believe Manual Work Items are created for Access Requests or Revokes if Provisioning is disable, but is that a requirement, or is creating manual work items optional?
Hi @gmilunich! Thanks for that input. I’ve created a ticket to review our provisioning documentation and provide more context around the source features attribute and turning provisioning off for a source.
Hi there, @gmilunich! I wanted to let you know that we are still investigating this. I appreciate your patience and hope to have the Provisioning documentation updated soon.
Hi there, @gmilunich! Thank you for your patience and helping us improve our documentation. Based on your feedback, we’ve updated the Setting up Provisioning section of our documentation. Please let us know if you have any questions or more feedback.
