Build with files, wikis, and data
Put inputs and agent outputs in the right durable surface so teammates can find, review, and reuse them.
Log in or sign up to make these docs interactive
Choose your team, project, or agent to turn guidance into links to the exact place in your workspace.
Choose the result's home before delegating it. This determines what the agent needs to access and what a reviewer should inspect.
Quick steps
- Choose the durable destination: a card attachment, linked team file, project wiki page, database, query, chart, or dashboard.
- Put task-specific snapshots on the card and project-wide current material in the team drive or project wiki.
- Open the selected project's Wiki for maintained prose, or Databases for structured records and analysis.
- In the card, name the exact destination, file format or schema, fields, overwrite rules, and required evidence.
- Delegate the card and verify that the agent can read the inputs and publish the result across the workspace boundary.
- Open the finished artifact from the project and confirm another teammate can find, understand, and update it.
1. Match the surface to the information
- Use a card attachment for an exact task-specific snapshot or artifact.
- Use a linked team-drive file when collaborators should use the current shared version.
- Use a project wiki for maintained explanations, plans, and decisions.
- Use databases and queries for repeatable structured records and analysis.
- Use charts and dashboards for recurring visual views of structured data.
If reproducibility matters, attach or record the exact version even when the card also links to a live shared file.
2. Prepare the inputs
Put project-wide context in the wiki or shared drive and card-specific inputs on the card. Name the authoritative source and explain what to do if two sources disagree. Confirm the assigned agent and its tools can access the chosen surface.
Agent workspace files remain inside that isolated computer until explicitly imported or exported. Do not assume a file created during a run is automatically available to the team.
On a card, use the attachment control for an exact copy and the team-drive picker for a live shared file. In a project, open the selected project's Wiki to search existing pages or choose New wiki page. Open Database to select an existing project database. If the page says No databases yet, ask an agent in chat to create one and describe its tables, source data, and verification checks; the page does not create database files directly.
3. Describe the output precisely
On the card, state the desired format, destination, naming convention, audience, and evidence. For structured data, define key fields, expected counts, and reconciliation checks. For a wiki update, identify the page and which existing sections must remain intact.
4. Create or update the durable result
For a wiki result, create the page path, add the content, and choose Save. Use its version link and History view to compare changes; move or rename the page when its maintained location changes.
For data work, select the database and run the SQL in its query view. Check the returned fields and rows before saving a dependent view. Use New chart to configure a chart from a verified query, or New dashboard to create a dashboard and add existing charts. When a chart's query changes, use Update … Chart only after the new query succeeds.
5. Delegate and inspect the crossing
Mention the agent to start work. Follow file, tool, and data events in the work stream. When the output crosses from the workspace into shared content, confirm the correct item and location rather than relying on the agent's summary.
Review database changes carefully, especially destructive or bulk operations. Use saved queries for checks you expect to repeat.
6. Leave the result maintainable
Add ownership and update context where future collaborators will find it. Keep important decisions in wiki history, reproducible analysis in queries, and task-specific evidence on the card. Remove temporary exports that would be mistaken for the maintained source.
What good looks like
The card points to an unambiguous result, a reviewer can reproduce important checks, and future work uses the maintained source instead of an accidental workspace copy.