When new access is granted on a source where a user does not already have an account, Identity Security Cloud automatically includes account creation in the provisioning. This applies whether provisioning started from an access request or from automated role or lifecycle state assignment.
When looking at the documentation, the 3rd paragraph currently reads:
On direct connect sources, Identity Security Cloud automatically creates the account based on the configurations in the Create Account page. For flat file sources, Identity Security Cloud creates a provisioning task containing the attribute values for the new account and assigns it to the source owner, so they can create the account manually.
What is not well documented is how the manual task process is expected to work and what the flow is from request to completed.
This document has some details on completing a request from an end-user standpoint:
Hi Geoff! Thanks for the feedback! I’ve created SAASDOCS-8080 to include more information about the manual task process in the administrator documentation. We’ll update this thread when that’s completed.
Hi @gmilunich, Thanks again for your feedback and helping us improve our documentation. We have updated the documentation to make it clearer as to why manual tasks are created for flat file sources. Due to the manual task needing to be actioned on the 3rd party system we are unable to provide any further details as to how to complete the task.
Thanks for the update. I see that you’ve called out the Delimited File Source directly for this, but won’t this be the same process for other sources if you remove the “PROVISIONING” flags from the source so that it no longer acts as a direct source?
Additionally, I do understand that there is no way to know how the 3rd party system works, I was more looking for what the process within ISC would look like from Provisioning Request to notifying the user, then once the user comes back in to mark it as completed.
Additionally, I see you mention that the tasks go to the Source Owner, but will they also go to the Governance Group for Source Management also?
Hi Geoff! Thank you for your additional input. We’ve created a Jira issue to track the effort and we’ll update the comment thread when it’s been addressed: SAASDOCS-8343
2 posts were split to a new topic: Source Account Provisioning Tasks Email Notifications
Hi @gmilunich. Thank you for your additional input. This appears to be a request to update the product. I’ve moved your comment to our Idea Discussions category for greater help from the community.