# Source Account Provisioning Tasks Email Notifications

**URL:** <https://developer.sailpoint.com/discuss/t/source-account-provisioning-tasks-email-notifications/89242>\
**Category:** Idea Discussions\
**Tags:** sailpoint-identity-security\
**Created:** [November 11, 2024, 4:52pm UTC](https://developer.sailpoint.com/discuss/t/source-account-provisioning-tasks-email-notifications/89242 "2024-11-11T16:52:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![GraemeF](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/graemef/32/11412_2.png) [@GraemeF](https://developer.sailpoint.com/discuss/u/GraemeF)\
**Post date:** [November 11, 2024, 4:52pm UTC](https://developer.sailpoint.com/discuss/t/source-account-provisioning-tasks-email-notifications/89242/1 "2024-11-11T16:52:21Z")

</div>

Hi @gmilunich, Thanks again for your additional feedback and helping us improve our documentation. We have updated the [documentation](https://documentation.sailpoint.com/saas/help/provisioning/create_profile.html) to make it clear that removing the PROVISIONING flag on a direct source will cause it to create provisioning tasks for accounts to be manually created, and that an email notification will be sent to the source owner.

Having checked with our product team I can also confirm that tasks and emails will only be sent to the source owner, and will not be sent to the governance group.

---

<div class="post-metadata">

**Author:** ![gmilunich](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/gmilunich/32/8431_2.png) [@gmilunich](https://developer.sailpoint.com/discuss/u/gmilunich)\
**Post date:** [November 11, 2024, 5:29pm UTC](https://developer.sailpoint.com/discuss/t/source-account-provisioning-tasks-email-notifications/89242/2 "2024-11-11T17:29:47Z")

</div>

> [@GraemeF](#):
>
> Having checked with our product team I can also confirm that tasks and emails will only be sent to the source owner, and will not be sent to the governance group.

Ok, this seems like a place where the product can be improved, because in many cases the Source Owner is the user on the IAM Team who’s job it is to maintain the Source configuration in ISC, and there is a team of individuals that manage the source itself in regards to the manual provisioning/Deprovisioning/management.

Do you know if the emails will be sent to the Source Sub-admins as well?
