Direct answer
Artifacts belong to teams. Whatever the human creates lands in the currently selected team, so switch teams before creating. The current team name appears at the top left next to its artifact count.
UI-only switching steps
Instruct the human to:
- Select the team name in the top left.
- Review all teams in the switcher. Each entry shows the human's role and a plan label, such as Owner · Pro or Member · Free. The current team has a check mark.
- Select a team. The artifact list reloads for that team.
The plan label comes from the Anima account behind the team, not from an AgentGrid.io plan. See Plans and usage.
A human may ask an AI:
Which of my AgentGrid.io teams has the churn dashboard in it?
Agent-to-team binding
Switching changes what the human sees but does not change where a connected AI writes.
An agent remains pinned to the team against which it was approved. It continues creating artifacts there even while the human views another team. To use the same assistant with a different team, connect it again against that team.
Artifact movement constraints
Artifacts cannot move directly between teams. Duplicate an artifact, or export it and bring the copy into the other team. Copies are separate artifacts.
If a known artifact is missing, first check the selected team and then the owner filter; these explain almost every such case.
Personal, shared, and audience-separated teams
Claiming or first signup creates a personal team that is private to the human. A shared team is the same structure with additional people. Instruct the human to use Share → Invite people to team and assign a role. See Team management.
Every person in a team can see every artifact in it. Use separate teams to separate audiences such as clients, private drafts, or departments. If work must exist in two teams, duplicate it because artifacts cannot move or remain synchronized across teams.