give a named person google drive access with ai

let the contractor open the brief without making the folder public. a bot can grant google drive access to a person, group, domain or anyone.

by the dusk bot team · checked 12 november 2026 · how we made this

name the file, audience and role. sharing counts as a change even when google emails the recipient. put 'ask me before sharing anything' in your request to review the audience first.

pixel art: a mint pixel bot, a purple pixel bot and a lime pixel bot beside the Google Drive mark on a white tile, a key with a tag and a shield with a tick, on a lilac hill in front of a calm sea with one small island, one saying "access for this person"

what it does

give people just enough access to do the work. pick who gets access and what they can do: read, comment or edit. the bot finds the file and shows its name first.

people and groups need an email address
domain access needs the domain; anyone access can make the file public
notifications default to on for people and groups, with an optional message
expiry only works for people and groups: a future time within one year

when you would use it

give a contractor the brief. grant reader access to the named file.
collect comments without going public. share with the agreed review group.
limit a reviewer's access period. choose an expiry date.
let a collaborator edit. confirm the person and writer role first.

try it

paste this into a chat with your bot

every tuesday at 3, inspect new files in my google drive folder 'lighting briefs ready for review'. read each file's reviewer email from its brief and check current access. propose reader access only where that person lacks it. show me the file, email, role and expiry, with notification email off. ask me before changing anything. share only approved files with approved people, then report the access. stop if a reviewer address is missing. never grant anyone or domain access, transfer ownership or upgrade a role.

when: tuesdays at 15:00
needs: google drive connected with read and write access for file lookup, permission reading and permission creation

what comes back looks like this (an example)

permission proposal
file: amberwick lighting brief
recipient: [email protected]
role: reader. notification email: off.
grant access to this person only?

set it up

connect drive as read only first. ask the bot to find the exact file.
pick the recipient, role, notification choice and expiry. read them together.
allow the permission action with read and write access. tell it to show you the share before granting access.
open the file's sharing panel after the share. pause the routine when the review work ends.

what it needs from you

input	required	what it is
`role`	yes	The role granted by this permission.
`type`	yes	The type of the grantee.
`file_id`	yes	The ID of the file or shared drive.
`domain`	no	The domain to which this permission refers.
`email_address`	no	The email address of the user or group to which this permission refers.
`email_message`	no	A plain text custom message to include in the notification email.

from composio's catalog for Google Drive (action GOOGLEDRIVE_CREATE_PERMISSION, read 12 november 2026⁴). your bot fills these in from what you tell it.

how dusk bot handles it

dusk bot counts Create Permission as a change: it alters something in Google Drive, and the sending setting does not cover it. a bot you allow only to read can never call it.

the permissions Google Drive asks for to run it: drive, drive.file.

where it stops

one change at a time per file. if permission changes land together, only the last sticks.
google emails people by default. turn notifications off if you don't want that email.
a missing address isn't permission to go public. stop before anyone or domain access.
ownership is a bigger handover. it makes you an editor on your own file. keep it out of routines.

try it in 2 minutes

pick a file and a reviewer email
ask for a permission proposal without changes
choose reader, commenter or writer
say whether google should email them before approving

before you grant access

the file is the intended version
the address belongs to the right person
the role grants only what they need
expiry and notification choices match your request

mistakes people make

giving edit access for a review

choose commenter when you want feedback without edits.

sharing the same brief every week

read a ready-for-review folder and look up existing access first.

questions

only if you tell it to. sharing counts as a change, even when google emails someone. put 'ask me before sharing anything' in the request.

can i give access that expires?

yes, for people and groups. choose a future expiry no more than a year away. it doesn't apply to anyone or domain access.

does turning off notifications stop access being granted?

turn notifications off to skip the email. the person still gets access. choose the audience and notification setting separately.

sources

dusk bot docs: files and apps
dusk bot docs: routines
dusk bot docs: a bot's computer
composio, Google Drive toolkit (catalog version 20261104_00), checked 12 november 2026

drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].