# Provisioning Policy Disable

**URL:** <https://developer.sailpoint.com/discuss/t/provisioning-policy-disable/3552>\
**Category:** SHF Discussion and Questions\
**Created:** [March 27, 2022, 4:07am UTC](https://developer.sailpoint.com/discuss/t/provisioning-policy-disable/3552 "2022-03-27T04:07:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ethompson](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/ethompson/32/17298_2.png) [@ethompson](https://developer.sailpoint.com/discuss/u/ethompson)\
**Post date:** [March 27, 2022, 4:07am UTC](https://developer.sailpoint.com/discuss/t/provisioning-policy-disable/3552/1 "2022-03-27T04:07:19Z")

</div>

Is there a difference between having an attribute on the Create Profile set as Disable vs omitting the value on the profile?

---

<div class="post-metadata">

**Author:** ![gustavo\_mariscal](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/gustavo_mariscal/32/628_2.png) [@gustavo\_mariscal](https://developer.sailpoint.com/discuss/u/gustavo_mariscal)\
**Post date:** [March 29, 2022, 8:19pm UTC](https://developer.sailpoint.com/discuss/t/provisioning-policy-disable/3552/2 "2022-03-29T20:19:17Z")

</div>

Hi Edward,

in both cases IdentityNow is not going to include the attribute in the provisioning plan but if the attribute is in the create profile you can enable the attribute as required, of course you can add an attribute on the create profile in the future or remove a disabled attribute.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [July 19, 2023, 2:22pm UTC](https://developer.sailpoint.com/discuss/t/provisioning-policy-disable/3552/3 "2023-07-19T14:22:49Z")

</div>