# NetSuite Access Request Prerequisite Validation in SailPoint

**URL:** <https://developer.sailpoint.com/discuss/t/netsuite-access-request-prerequisite-validation-in-sailpoint/225294>\
**Category:** SHF Discussion and Questions\
**Tags:** sailpoint-identity-security, saas-connector\
**Created:** [October 12, 2026, 9:23am UTC](https://developer.sailpoint.com/discuss/t/netsuite-access-request-prerequisite-validation-in-sailpoint/225294 "2026-10-12T09:23:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![spedduri](https://avatars.discourse-cdn.com/v4/letter/s/f17d59/32.png) [@spedduri](https://developer.sailpoint.com/discuss/u/spedduri)\
**Post date:** [October 12, 2026, 9:23am UTC](https://developer.sailpoint.com/discuss/t/netsuite-access-request-prerequisite-validation-in-sailpoint/225294/1 "2026-10-12T09:23:31Z")

</div>

Hi Team,

Greetings for the day!

We are currently working on the NetSuite SaaS connector. The NetSuite team has a requirement whereby, before a user can submit or proceed with an access request, the **GetAccess** attribute must first be set to **“True”** and send email value must also be updated to **“True”**. Only after these conditions are met can the access request be initiated.

This is the process currently followed by the NetSuite team. Could you please advise how this workflow or validation can be implemented in SailPoint?

Thank you.

---

<div class="post-metadata">

**Author:** ![suraj\_gorle](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/suraj_gorle/32/35158_2.png) [@suraj\_gorle](https://developer.sailpoint.com/discuss/u/suraj_gorle)\
**Post date:** [October 12, 2026, 9:29am UTC](https://developer.sailpoint.com/discuss/t/netsuite-access-request-prerequisite-validation-in-sailpoint/225294/2 "2026-10-12T09:29:23Z")

</div>

Hi @spedduri ,

As far as I know, SailPoint ISC doesn’t have a built-in way to block someone from submitting an access request based on an attribute value. There are a few ways to get the same result, though:

1. **Set the values during provisioning.** In NetSuite, “Give Access” and “Send Email” are part of the employee record. If they just need to be `true` for the access to work, set them in the connector’s create/update operation or with a Before Provisioning rule, so the requester never has to touch them.
2. **Validate with a Workflow.** Use the Access Request Submitted (or Dynamic Approval) trigger, check `getAccess` and `sendEmail`, and deny or reroute the request if either isn’t `true`. This runs after submission, so it can reject the request but not stop it from being submitted.
3. **Add an approval step.** If someone has to set the values manually, make the NetSuite team an approver so they fix the attributes first, then approve.

Thanks.

---

<div class="post-metadata">

**Author:** ![Jerinhrb04](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/jerinhrb04/32/42240_2.png) [@Jerinhrb04](https://developer.sailpoint.com/discuss/u/Jerinhrb04)\
**Post date:** [October 13, 2026, 12:44pm UTC](https://developer.sailpoint.com/discuss/t/netsuite-access-request-prerequisite-validation-in-sailpoint/225294/3 "2026-10-13T12:44:06Z")

</div>

Hello @spedduri ,

Looks like the approaches suggested by @suraj_gorle is good. One additional point to consider is whether **`giveAccess`** and **`sendEmail`** are truly prerequisites for _every_ NetSuite access request, or whether they are simply part of the NetSuite account onboarding process. The Oracle NetSuite connector supports both attributes as provisioning attributes, with `giveAccess` specifically supported for update operations. If these settings are required for all NetSuite users, I would be inclined to manage them automatically during account creation/update rather than validating them on every request. This keeps the access request process simpler and avoids users seeing avoidable request rejections. [[documentat…lpoint.com]](https://documentation.sailpoint.com/saas/help/provisioning/index.html)

Also, if the business wants to ensure the values are set before granting access, one option could be to create a “NetSuite Account Enablement” access item/process that sets `giveAccess=true` and `sendEmail=true`. Once completed, users can request additional NetSuite roles/access normally. That said, if the requirement is specifically to **prevent** access from being granted when those attributes are not enabled, then the workflow/approval approach already suggested would be the appropriate control.

---

<div class="post-metadata">

**Author:** ![vikaspawar0303](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/vikaspawar0303/32/34710_2.png) [@vikaspawar0303](https://developer.sailpoint.com/discuss/u/vikaspawar0303)\
**Post date:** [October 13, 2026, 11:32pm UTC](https://developer.sailpoint.com/discuss/t/netsuite-access-request-prerequisite-validation-in-sailpoint/225294/4 "2026-10-13T23:32:24Z")

</div>

@sravanthi1599 Create a custom workflow that:

1. User submits an access request.
2. Workflow checks the target NetSuite account.
3. If `GetAccess != True` or `SendEmail != True`:
  - Perform an account update provisioning action to set:
    - `GetAccess = True`
    - `SendEmail = True`

4. Wait for successful provisioning.
5. Continue with the access grant request.

This provides an automated end-to-end process.