Verwendet RFC 3339, wobei die generierte Ausgabe immer Z-normalisiert ist und 0, 3, 6 oder 9 Nachkommastellen verwendet. Andere Offsets als „Z“ werden ebenfalls akzeptiert. Beispiele: "2014-10-02T15:01:23Z", "2014-10-02T15:01:23.045123456Z" oder "2014-10-02T15:01:23+05:30".
RoleAndView
Ein Wrapper für die Rolle und Ansicht eines Zugriffsvorschlags.
JSON-Darstellung
{"role": string,"view": string}
Felder
role
string
Die vom Antragsteller vorgeschlagene Rolle. In Zukunft können neue Werte hinzugefügt werden, derzeit sind jedoch nur die folgenden möglich: * writer * commenter * reader
view
string
Gibt die Ansicht für diesen Zugriffsvorschlag an. Wird nur für Vorschläge ausgefüllt, die zu einer Ansicht gehören. published ist der einzige unterstützte Wert.
[[["Leicht verständlich","easyToUnderstand","thumb-up"],["Mein Problem wurde gelöst","solvedMyProblem","thumb-up"],["Sonstiges","otherUp","thumb-up"]],[["Benötigte Informationen nicht gefunden","missingTheInformationINeed","thumb-down"],["Zu umständlich/zu viele Schritte","tooComplicatedTooManySteps","thumb-down"],["Nicht mehr aktuell","outOfDate","thumb-down"],["Problem mit der Übersetzung","translationIssue","thumb-down"],["Problem mit Beispielen/Code","samplesCodeIssue","thumb-down"],["Sonstiges","otherDown","thumb-down"]],["Zuletzt aktualisiert: 2025-08-27 (UTC)."],[],[],null,["# REST Resource: accessproposals\n\n- [Resource: AccessProposal](#AccessProposal)\n - [JSON representation](#AccessProposal.SCHEMA_REPRESENTATION)\n- [RoleAndView](#RoleAndView)\n - [JSON representation](#RoleAndView.SCHEMA_REPRESENTATION)\n- [Methods](#METHODS_SUMMARY)\n\nResource: AccessProposal\n------------------------\n\nThe Access Proposal resource for outstanding access proposals on a file\n\n| JSON representation |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| ``` { \"fileId\": string, \"proposalId\": string, \"requesterEmailAddress\": string, \"recipientEmailAddress\": string, \"rolesAndViews\": [ { object (/workspace/drive/api/reference/rest/v3/accessproposals#RoleAndView) } ], \"requestMessage\": string, \"createTime\": string } ``` |\n\n| Fields ||\n|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `fileId` | `string` The file id that the proposal for access is on |\n| `proposalId` | `string` The id of the access proposal |\n| `requesterEmailAddress` | `string` The email address of the requesting user |\n| `recipientEmailAddress` | `string` The email address of the user that will receive permissions if accepted |\n| `rolesAndViews[]` | `object (`[RoleAndView](/workspace/drive/api/reference/rest/v3/accessproposals#RoleAndView)`)` A wrapper for the role and view of an access proposal. |\n| `requestMessage` | `string` The message that the requester added to the proposal |\n| `createTime` | `string (`[Timestamp](https://protobuf.dev/reference/protobuf/google.protobuf/#timestamp)` format)` The creation time Uses RFC 3339, where generated output will always be Z-normalized and uses 0, 3, 6 or 9 fractional digits. Offsets other than \"Z\" are also accepted. Examples: `\"2014-10-02T15:01:23Z\"`, `\"2014-10-02T15:01:23.045123456Z\"` or `\"2014-10-02T15:01:23+05:30\"`. |\n\nRoleAndView\n-----------\n\nA wrapper for the role and view of an access proposal.\n\n| JSON representation |\n|--------------------------------------------|\n| ``` { \"role\": string, \"view\": string } ``` |\n\n| Fields ||\n|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `role` | `string` The role that was proposed by the requester New values may be added in the future, but the following are currently possible: \\* `writer` \\* `commenter` \\* `reader` |\n| `view` | `string` Indicates the view for this access proposal. Only populated for proposals that belong to a view. `published` is the only supported value. |\n\n| Methods ------- ||\n|-------------------------------------------------------------------------------|---------------------------------------------|\n| ### [get](/workspace/drive/api/reference/rest/v3/accessproposals/get) | Retrieves an AccessProposal by ID. |\n| ### [list](/workspace/drive/api/reference/rest/v3/accessproposals/list) | List the AccessProposals on a file. |\n| ### [resolve](/workspace/drive/api/reference/rest/v3/accessproposals/resolve) | Used to approve or deny an Access Proposal. |"]]
