pub struct Permission {Show 16 fields
pub allow_file_discovery: Option<bool>,
pub deleted: Option<bool>,
pub display_name: Option<String>,
pub domain: Option<String>,
pub email_address: Option<String>,
pub expiration_time: Option<DateTime<Utc>>,
pub id: Option<String>,
pub inherited_permissions_disabled: Option<bool>,
pub kind: Option<String>,
pub pending_owner: Option<bool>,
pub permission_details: Option<Vec<PermissionPermissionDetails>>,
pub photo_link: Option<String>,
pub role: Option<String>,
pub team_drive_permission_details: Option<Vec<PermissionTeamDrivePermissionDetails>>,
pub type_: Option<String>,
pub view: Option<String>,
}Expand description
A permission for a file. A permission grants a user, group, domain, or the world access to a file or a folder hierarchy. For more information, see Share files, folders, and drives. By default, permission requests only return a subset of fields. Permission kind, ID, type, and role are always returned. To retrieve specific fields, see Return specific fields. Some resource methods (such as permissions.update) require a permissionId. Use the permissions.list method to retrieve the ID for a file, folder, or shared drive.
§Activities
This type is used in activities, which are methods you may call on this type or where this type is involved in. The list links the activity name, along with information about where it is used (one of request and response).
- create permissions (request|response)
- delete permissions (none)
- get permissions (response)
- list permissions (none)
- update permissions (request|response)
Fields§
§allow_file_discovery: Option<bool>Whether the permission allows the file to be discovered through search. This is only applicable for permissions of type domain or anyone.
deleted: Option<bool>Output only. Whether the account associated with this permission has been deleted. This field only pertains to permissions of type user or group.
display_name: Option<String>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 “Dana A.” * group - Name of the Google Group, such as “The Company Administrators.” * domain - String domain name, such as “cymbalgroup.com.” * anyone - No displayName is present.
domain: Option<String>The domain to which this permission refers.
email_address: Option<String>The email address of the user or group to which this permission refers.
expiration_time: Option<DateTime<Utc>>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: Option<String>Output only. The ID of this permission. This is a unique identifier for the grantee, and is published in the User resource as permissionId. IDs should be treated as opaque values.
inherited_permissions_disabled: Option<bool>When true, only organizers, owners, and users with permissions added directly on the item can access it.
kind: Option<String>Output only. Identifies what kind of resource this is. Value: the fixed string "drive#permission".
pending_owner: Option<bool>Whether the account associated with this permission is a pending owner. Only populated for permissions of type user for files that aren’t in a shared drive.
permission_details: Option<Vec<PermissionPermissionDetails>>Output only. Details of whether the permissions on this item are inherited or are directly on this item.
photo_link: Option<String>Output only. A link to the user’s profile photo, if available.
role: Option<String>The role granted by this permission. Supported values include: * owner * organizer * fileOrganizer * writer * commenter * reader For more information, see Roles and permissions.
team_drive_permission_details: Option<Vec<PermissionTeamDrivePermissionDetails>>Output only. Deprecated: Output only. Use permissionDetails instead.
type_: Option<String>The type of the grantee. Supported values include: * user * group * domain * anyone When creating a permission, if type is user or group, you must provide an emailAddress for the user or group. If type is domain, you must provide a domain. If type is anyone, no extra information is required.
view: Option<String>Indicates the view for this permission. Only populated for permissions that belong to a view. The only supported values are published and metadata: * published: The permission’s role is publishedReader. * metadata: The item is only visible to the metadata view because the item has limited access and the scope has at least read access to the parent. The metadata view is only supported on folders. For more information, see Views.
Trait Implementations§
Source§impl Clone for Permission
impl Clone for Permission
Source§fn clone(&self) -> Permission
fn clone(&self) -> Permission
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more