# Create Account / Provisioning Policy

**URL:** <https://developer.sailpoint.com/discuss/t/create-account-provisioning-policy/61150>\
**Category:** Connectivity Documentation Feedback\
**Tags:** va-con-docs\
**Created:** [June 3, 2024, 5:02pm UTC](https://developer.sailpoint.com/discuss/t/create-account-provisioning-policy/61150 "2024-06-03T17:02:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![DocsTeam](https://avatars.discourse-cdn.com/v4/letter/d/ecd19e/32.png) [@DocsTeam](https://developer.sailpoint.com/discuss/u/DocsTeam)\
**Post date:** [June 3, 2024, 5:02pm UTC](https://developer.sailpoint.com/discuss/t/create-account-provisioning-policy/61150/1 "2024-06-03T17:02:37Z")

</div>

When SailPoint provisions new accounts to an Atlassian Suite source, it uses the attributes on the Create Account page as instructions or a template for what to include in the account. This page is also referred to as the _provisioning policy_.

* * *
This is the companion discussion topic for the documentation at [https://documentation.sailpoint.com/connectors/atlassian/cloud/help/integrating\_atlassian\_cloud/create\_profile.html](https://documentation.sailpoint.com/connectors/atlassian/cloud/help/integrating_atlassian_cloud/create_profile.html)

---

<div class="post-metadata">

**Author:** ![joshb488](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/joshb488/32/11416_2.png) [@joshb488](https://developer.sailpoint.com/discuss/u/joshb488)\
**Post date:** [April 28, 2025, 2:41pm UTC](https://developer.sailpoint.com/discuss/t/create-account-provisioning-policy/61150/2 "2025-04-28T14:41:18Z")

</div>

A post was split to a new topic: [Atlassian Suite Cloud - Integration endpoints?](https://developer.sailpoint.com/discuss/t/atlassian-suite-cloud-integration-endpoints/116553)

---

<div class="post-metadata">

**Author:** ![joshb488](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/joshb488/32/11416_2.png) [@joshb488](https://developer.sailpoint.com/discuss/u/joshb488)\
**Post date:** [April 28, 2025, 2:42pm UTC](https://developer.sailpoint.com/discuss/t/create-account-provisioning-policy/61150/3 "2025-04-28T14:42:54Z")

</div>

Hi Nischal! Thank you for your input. This appears to be related to using the product features. I’ve moved your comment to our [ISC Discussions and Questions](https://developer.sailpoint.com/discuss/c/identity-security-cloud/discussion-and-questions/37) category for greater help from the community.

---

<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:** [April 29, 2025, 6:04pm UTC](https://developer.sailpoint.com/discuss/t/create-account-provisioning-policy/61150/4 "2025-04-29T18:04:23Z")

</div>

I think it would be helpful if the documentation for these connectors also includes the list of end points that the connector uses to accomplish it’s tasks. I think that is what @nadhikari_identitynow is looking for so that he can continue his testing outside of ISC to make sure that those endpoints are working. It would also be helpful for clients to be able to verify that they have given permissions to the Service Accounts to the proper endpoints. This is not just specific to this connector, but it would be good for all connectors that have REST Endpoints under the hood.

---

<div class="post-metadata">

**Author:** ![joshb488](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/joshb488/32/11416_2.png) [@joshb488](https://developer.sailpoint.com/discuss/u/joshb488)\
**Post date:** [April 30, 2025, 6:31pm UTC](https://developer.sailpoint.com/discuss/t/create-account-provisioning-policy/61150/6 "2025-04-30T18:31:36Z")

</div>

Hi Geoff. This is a good idea, and I can look into making it happen. I created CONDOCS-6653 to track this work. The team will update this thread when the work is completed.

-Josh
