Why Quin can't create or move a file in Google Drive

Quin can search a Drive file without being able to touch it, and that distinction matters more than it might seem. Read-only access is enough to find and reference a document, but creating a new file or moving one to a different folder needs a different level of permission entirely.

Reasons Quin might not be able to create or move a file

• Read-only access was granted during setup instead of full Drive permissions.
• The target folder doesn't exist yet, or the account doesn't have permission to add files to it.
• Access to Quin was revoked in Google Account settings without disconnecting the integration in Quin directly.
• A file restricted by special sharing permissions that limit what an outside integration can do with it.
• A recent permissions change that hasn't been reflected yet in the connection.

How Quin handles it

The permissions granted during setup determine what Quin can do with Drive, not just what it can see. Read-only access lets Quin search and reference files, but creating new documents or moving existing ones requires full permissions, granted the same way during the initial connection or by reconnecting later.

Say Quin can answer questions about what's in a Drive folder but returns an error when asked to create a new document there. That's usually a sign the integration was connected with read-only access rather than full permissions, not a sign something else is wrong.

Why this matters

Treating every Drive request the same, regardless of what it needs, makes a permissions issue look like a bug. Searching and creating are different capabilities that depend on different levels of access, and knowing which one a request needs is what makes a permissions error easy to diagnose instead of confusing. A search that works fine while creation fails isn't a partial malfunction; it's two different permissions doing exactly what they were granted to do.

Getting the most out of it

• Grant full Drive permissions during setup if creating or organizing files is part of what you want Quin to do.
• Reconnect the integration under Settings, then Integrations, if file creation or moves stop working unexpectedly.
• Check Google Account settings directly if the connection shows as disconnected, since access can be revoked there without Quin reflecting it right away.
• Distinguish between a search problem and a permissions problem before assuming the integration itself is broken.

Setting it up

Connect Google Drive under Settings, then Integrations, and choose full permissions rather than read-only access if file creation and organization matter to your workflow. Read-only access can always be upgraded later by reconnecting with broader permissions.