A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: "2014-10-02T15:01:23Z" and "2014-10-02T15:01:23.045123456Z".
A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: "2014-10-02T15:01:23Z" and "2014-10-02T15:01:23.045123456Z".
Optional. Additional email addresses to be notified based on actions taken.
etag
string
An etag is used for optimistic concurrency control as a way to prevent simultaneous updates to the same entitlement. An etag is returned in the response to entitlements.get and the caller should put the etag in the request to entitlements. so that their change is applied on the same version. If this field is omitted or if there is a mismatch while updating an entitlement, then the server rejects the request.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-05-21 UTC."],[[["An entitlement defines user eligibility for predefined access, potentially requiring an approval workflow."],["The JSON representation outlines the structure of an entitlement, including fields like name, creation time, eligible users, and approval workflow."],["Entitlements specify the maximum duration of access, the state of the entitlement, and how requesters should provide justifications."],["Various methods are available to manage entitlements, such as creating, deleting, getting, listing, patching, and searching for entitlements."],["Entitlements use an 'etag' field for optimistic concurrency control during updates, preventing conflicts."]]],[]]