What does google_drive.permission.granted prove?

Prove that Drive gave the intended person the intended access to the file. A permission that exists is not a permission for the right person. This level reads the address, the type and the role of the grantee.

What is the intent?

Give the person the stated role on the file.

What is the subject and the action?

Which false successes give CONTRADICTED?

• duplicate side effect
• other
• pre existing state
• wrong subject

The signed contract states the exact conditions, the evidence and the timing. The runtime reads them. The page states the promise.

Where do these rules come from?

• google_drive.openapi#/paths/~1drive~1v3~1files~1{fileId}~1permissions/post: google_drive.openapi, retrieved 2026-09-09
• google_drive.openapi#/paths/~1drive~1v3~1files~1{fileId}~1permissions/post/responses/200: google_drive.openapi, retrieved 2026-09-09
• google_drive.docs.sharing#share-files-folders-and-drives/create-a-permission: google_drive.docs.sharing, retrieved 2026-09-09
• google_drive.docs.sharing#share-files-folders-and-drives/a-response-returns-a-subset-of-the-members: google_drive.docs.sharing, retrieved 2026-09-09
• google_drive.events#/events/drive.file.update.permissions: google_drive.events, retrieved 2026-09-09
• google_drive.docs.push#push-notifications/the-changed-members: google_drive.docs.push, retrieved 2026-09-09
• google_drive.openapi#/paths/~1drive~1v3~1files~1{fileId}~1watch/post: google_drive.openapi, retrieved 2026-09-09