Updates a permission with patch semantics. Warning: Concurrent permissions operations on the same file are not supported; only the last update is applied.

Scopes

You will need authorization for at least one of the following scopes to make a valid call:

  • https://www.googleapis.com/auth/drive
  • https://www.googleapis.com/auth/drive.file

If unset, the scope for this method defaults to https://www.googleapis.com/auth/drive. You can set the scope for this method like this: drive3 --scope <scope> permissions update ...

Required Scalar Arguments

  • <file-id> (string)
    • The ID of the file or shared drive.
  • <permission-id> (string)
    • The ID of the permission.

Required Request Value

The request value is a data-structure with various fields. Each field may be a simple scalar or another data-structure. In the latter case it is advised to set the field-cursor to the data-structure's field to specify values more concisely.

For example, a structure like this:

Permission:
  allow-file-discovery: boolean
  deleted: boolean
  display-name: string
  domain: string
  email-address: string
  expiration-time: string
  id: string
  kind: string
  pending-owner: boolean
  photo-link: string
  role: string
  type: string
  view: string

can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.

  • -r . allow-file-discovery=false
    • Whether the permission allows the file to be discovered through search. This is only applicable for permissions of type domain or anyone.
  • deleted=true
    • Output only. Whether the account associated with this permission has been deleted. This field only pertains to user and group permissions.
  • display-name=sanctus
    • Output only. The "pretty" name of the value of the permission. The following is a list of examples for each type of permission: * user - User's full name, as defined for their Google account, such as "Joe Smith." * group - Name of the Google Group, such as "The Company Administrators." * domain - String domain name, such as "thecompany.com." * anyone - No displayName is present.
  • domain=invidunt
    • The domain to which this permission refers.
  • email-address=sit
    • The email address of the user or group to which this permission refers.
  • expiration-time=sed
    • The time at which this permission will expire (RFC 3339 date-time). Expiration times have the following restrictions: - They can only be set on user and group permissions - The time must be in the future - The time cannot be more than a year in the future
  • id=duo
    • Output only. The ID of this permission. This is a unique identifier for the grantee, and is published in User resources as permissionId. IDs should be treated as opaque values.
  • kind=et
    • Output only. Identifies what kind of resource this is. Value: the fixed string &#34;drive#permission&#34;.
  • pending-owner=true
    • Whether the account associated with this permission is a pending owner. Only populated for user type permissions for files that are not in a shared drive.
  • photo-link=et
    • Output only. A link to the user's profile photo, if available.
  • role=sed
    • The role granted by this permission. While new values may be supported in the future, the following are currently allowed: * owner * organizer * fileOrganizer * writer * commenter * reader
  • type=justo
    • The type of the grantee. Valid values are: * user * group * domain * anyone When creating a permission, if type is user or group, you must provide an emailAddress for the user or group. When type is domain, you must provide a domain. There isn't extra information required for an anyone type.
  • view=sadipscing
    • Indicates the view for this permission. Only populated for permissions that belong to a view. 'published' is the only supported value.

About Cursors

The cursor position is key to comfortably set complex nested structures. The following rules apply:

  • The cursor position is always set relative to the current one, unless the field name starts with the . character. Fields can be nested such as in -r f.s.o .
  • The cursor position is set relative to the top-level structure if it starts with ., e.g. -r .s.s
  • You can also set nested fields without setting the cursor explicitly. For example, to set a value relative to the current cursor position, you would specify -r struct.sub_struct=bar.
  • You can move the cursor one level up by using ... Each additional . moves it up one additional level. E.g. ... would go three levels up.

Optional Output Flags

The method's return value a JSON encoded structure, which will be written to standard output by default.

  • -o out
    • out specifies the destination to which to write the server's result to. It will be a JSON-encoded structure. The destination may be - to indicate standard output, or a filepath that is to contain the received bytes. If unset, it defaults to standard output.

Optional Method Properties

You may set the following properties to further configure the call. Please note that -p is followed by one or more key-value-pairs, and is called like this -p k1=v1 k2=v2 even though the listing below repeats the -p for completeness.

  • -p remove-expiration=boolean

    • Whether to remove the expiration date.
  • -p supports-all-drives=boolean

    • Whether the requesting application supports both My Drives and shared drives.
  • -p supports-team-drives=boolean

    • Deprecated: Use supportsAllDrives instead.
  • -p transfer-ownership=boolean

    • Whether to transfer ownership to the specified user and downgrade the current owner to a writer. This parameter is required as an acknowledgement of the side effect.
  • -p use-domain-admin-access=boolean

    • Issue the request as a domain administrator; if set to true, then the requester will be granted access if the file ID parameter refers to a shared drive and the requester is an administrator of the domain to which the shared drive belongs.

Optional General Properties

The following properties can configure any call, and are not specific to this method.

  • -p $-xgafv=string

    • V1 error format.
  • -p access-token=string

    • OAuth access token.
  • -p alt=string

    • Data format for response.
  • -p callback=string

    • JSONP
  • -p fields=string

    • Selector specifying which fields to include in a partial response.
  • -p key=string

    • API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token.
  • -p oauth-token=string

    • OAuth 2.0 token for the current user.
  • -p pretty-print=boolean

    • Returns response with indentations and line breaks.
  • -p quota-user=string

    • Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters.
  • -p upload-type=string

    • Legacy upload protocol for media (e.g. "media", "multipart").
  • -p upload-protocol=string

    • Upload protocol for media (e.g. "raw", "multipart").