**Requirements:** Admin or Editor role. Only for spreadsheet or file-storage integrations (Google Sheets/Drive, Excel/OneDrive). A connection having the "Add row" or "Upload file" action allowed isn't enough by itself: a flow piece that WRITES also needs you to explicitly register WHICH sheet or folder it can do that in. It's a second lock, meant so that you never accidentally enable writing to everything that account can see. Press **"Resources"** on the connection's row to manage it. 1. Press **"+ Add sheet or folder"**. 2. Paste the **link or identifier** — the hint tells you where to copy it from in Google. 3. If it's a spreadsheet, give the exact **tab name**. 4. Check **"Allow the flow to write here"** if you need write access — if you leave it unchecked, the resource stays read-only. 5. Press **"Register"** — the platform checks access LIVE before saving anything. The check is real, against the provider — a resource is never accepted blindly. If the document doesn't exist, isn't shared with the platform, or only has read permission when you asked for write, the error tells you the exact cause, next to the field: Once registered, resources appear in the list with their type (Sheet/Folder), their permission (Read / Read and write) and the buttons to change the permission or remove them. In the **builder's inspector** (Manual 55, section 3.4), the sheet or folder field of a piece that writes is a **closed** dropdown — it only offers the chosen connection's resources that have write permission, never a free-text field where you can paste any identifier. > **Note — Google Drive: registering works, writing doesn't yet** > > You can register Drive folders with write permission today. Actually performing that write (uploading a file or creating the folder from a flow) doesn't work yet: the platform's permission with Google still needs widening — the builder's own inspector warns you when it affects your piece, and the flow can still be saved, it just won't run that action until then.