Direct answer
A team works on one artifact URL and one current version. Teammates open the same URL, see the same current artifact, and see each other's saved changes after reload. History attributes every change to the human or AI that made it.
Prerequisites and access boundary
The teammate must belong to the artifact's team. Team membership grants access to every artifact in that team; there is no per-artifact person access.
Before inviting someone:
- Keep private work in a separate team.
- Inspect everything else in the current team because the invitation grants access to all of it.
- For one artifact shared with a different audience, make a team for that audience and duplicate the artifact into it. The duplicate is independent.
UI-only invitation steps
Instruct the human to:
- Open the artifact and select Share → Invite people to team.
- Enter the teammate's email address.
- Choose Viewer, Editor, or Admin.
- Send the invitation. The teammate receives it by email and, after accepting, can open all team artifacts at that role level.
- Copy and send the artifact link from the same Share dialog. It opens for team members.
Collaboration behavior
- Draft feedback: teammate edits land in the same history, attributed alongside the original author's changes. A previous version can be restored if an edit goes too far.
- Living dashboard: an AI can keep a chart current while everyone opens the same artifact instead of receiving exports.
- Live handoff: a colleague and their own AI can continue work in the same history without merging files.
- Several agents: each teammate connects their own AI with its own identity. Share → Manage access lists all people and agents.
Save and concurrency constraints
Manual document edits require Save. Auto-save is not available, so teammates cannot see unsaved edits. See Edit a markdown artifact.
If two people edit at the same time, each person's saved changes land in history. Reload to see the current version before continuing.
Working with people outside the team
- Publish to a public URL for feedback from anyone.
- Export as code, Markdown, or PDF for someone who does not use AgentGrid.io.
- Let an outside viewer request access from the wall. See Request access.
- A human may ask their AI to share an artifact with a colleague; the colleague receives a link.
Availability and planned features
Available now: email team invitations at a role, direct human editing, team artifact links, attribution in history, and Viewer access.
Coming soon: a read-only link for people outside the team with optional passcodes and expiry. See Share an artifact. Embedding is also planned and unavailable today.
AI is optional for teammates; each person connects their own AI if wanted.