In a scenario with a Request entity having a status attribute with values Draft, Submitted, and Approved, what would a Customer user with [Status = Draft] access see?

In this scenario, a Customer user with the status set to Draft would have access to all requests that are also in the Draft status. This is based on the user’s access rights, which typically allow visibility of records that match their current status settings. Since the user is specifically filtering for requests that are in Draft, they would be able to view all requests that meet that condition.

This access level is essential for ensuring that users can manage and interact with their own drafts while maintaining the necessary visibility to processes still in progress. Being able to see only their own Draft requests allows for effective management and organization of requests before they progress to the next status levels—Submitted and Approved—which are not applicable to this user at this time.

The other options present views that do not align with the access level connected to the Draft status. For example, the user would not see only Submitted requests, all requests including Approved ones, or have no visibility at all, as these do not correspond with the entitlement linked to their current Draft status.