Use shared notes as context for a chosen agent
Choose the material, task, provider and write permissions deliberately.
Start with a useful record
Write the decision, its sources and the constraints that matter. Shared notes are the durable record; an agent still needs to load relevant context for each task. A model does not automatically remember the whole workspace.
Authorize a narrow scope
Select the notes you are allowed to share and a specific task. Permission to read a team note may not include organizational permission to transmit it to an external provider. Notes sharing, operating-system access and provider settings are different controls.
Understand where plaintext goes
A locally running tool can still use a cloud model. Selected plaintext may be sent to that provider under its terms and settings. Local files do not establish local inference, training confidentiality or a retention guarantee.
Review before carrying the work forward
Inspect the proposed change and its source material. For direct file writes, use the supported change-detection, reconciliation and recovery path. A scoped read does not prove safe writeback. Verify the exact tool, operating system and app build before using a named workflow.
Close the human loop
Have a teammate question and refine the result in Notes. Explicitly load the updated authorized record in the next agent task. Revoking access can limit future reads; it does not retract text already copied or sent.