New Capability: Start Date in Access Requests

This capability is brought to you by :aha: Idea GOV-I-1681 and :aha: Idea GOV-I-1034

Description

We are pleased to announce the upcoming release of a new option to help your organization better manage your least privilege requirements in access requests: access start date and time.

The access start date and time feature allows you to approve future access needs in advance. Provisioning is then automatically delayed until the specified date and time, ensuring access is granted only when needed. Common use cases include:

  • Pre-hire (joiner) processes
  • Job change (mover) processes
  • Scheduled project starts
  • After hours IT maintenance or deployment activities that require short-term elevated access

Applying a Start Date

You can optionally provide an access start date and time for any access request. This setting cannot be made mandatory because the start date is tied to when the access is assigned to a user, not to the access privilege itself.

When an access start date is specified, any configured max duration requirement is applied for the access end date based on the selected start date and time instead of the moment of request.

Tip: Users who need the max allowed time period for access with tight max durations can use this feature to plan ahead and have approvals completed before their needed time window starts.

As with our earlier access end date/time release, the request page will default the time zone to the requester’s browser time zone, but they have the ability to override that if they prefer to specify the revocation time in another time-zone context.

Note: Requesters don’t need to shift time zones for the benefit of the requestee or approver – the UI will automatically display the end time in the viewer’s browser time zone on pages like the approval page or the My Access page.

Date Changes

Assignment start dates can be altered as needed, until the designed start date and time arrives.

Note: You cannot add a start date after the fact, as the access will already have been provisioned.

  • Users can request a new start date for themselves on the My Access page.
  • Managers can request start date changes on the My Team page.
  • Admins and Access Revokers can adjust start dates on the Admin > Identities > Access page.

All date-change requests must comply with any specified max duration requirements, enforced from the moment of the new start date. End dates can be edited in the same operation.

All start date change requests will go through the configured approvals before being applied.

  • Any time a start date moves earlier, whether accompanying end date changes results in shortening, lengthening, or no change to access duration, add-access approval is required.
  • When start date is shifted later but the total duration stays the same or becomes longer, add-access approval is required.
  • When start date is shifted later and the total duration becomes shorter, remove-access approval is required. (If you have not configured the separate revocation approval requirements, that will mean no approval is required for shortening a duration by moving the start date outward.)

Date Change through Re-Request

As before, users can also request an access date change by submitting a new request for the access with a different start and end date through the Request Center. Since Request Center is not contextually aware of existing assignments, all requests submitted this way, even those that shorten the duration, will be processed under the add-access approval flow, but the approver will still see that the request is for a date change and will see the old and new end dates in the approval details.

Approval Detail

Similar to end date changes, start date changes are clearly presented to the approver as a date modification, not a brand new access request. The approver will see a Modify operation and a specific Access Date Change marker on the approval card. In the approval details, the prior start and end dates are shown alongside the new dates for easy comparison.

Who is affected?

This is being rolled out to all suites customers.

Important Dates

Important Dates

Sandbox rollout: Available now!

Production rollout: May 27 - June 1, 2026

Will be possible to set start date with API or using workflow?

1 Like

Sounds good!

Please also include the API calls for this, as that would be the way we would use this feature.

This feature is working when the role does not require approval. But if a role require approval, then approving the access request it is immediately going to provision phase, not waiting for Start date to arrive.

yes, it is possible. the field name is “startDate” in the access request submit api. pass the future start date against the attribute" “startDate”, just parallel to the existing attribute “removeDate”

The GUI is getting messy/noisy and confusing to end users.

What would be great would be a way to turn this off, and enable it on a per Entitlement/AR/Role/App.

2 Likes

Although it might be a good feature for some of the connected applications, it’s not the case for disconnected applications or where such info (sunrise, sunset) will confuse approvers.
I really would like to be able to customize access profiles the way we would like to configure. Access Sunrise and Sunset should be customized per access profile to be either mandatory fields, or optional, or not visible at all.

1 Like