# Create a team and add people Source: https://www.hyperagent.com/docs/concepts/teams/create-a-team > For AI agents: the documentation index is at https://www.hyperagent.com/llms.txt and the complete documentation in one file at https://www.hyperagent.com/llms-full.txt. Any docs page is also served as Markdown by appending `.md` to its URL. Make a team workspace, invite people by email or a shared link, assign the role each person needs, and manage membership as it changes. A team starts as an empty workspace. Create it, bring people in, and give each person the [role](https://www.hyperagent.com/docs/concepts/teams/members) that matches their responsibility. Create the workspace, invite people by email or a reusable link, and assign a role as each person joins. Membership and roles stay yours to change as the group evolves. ## Create the team [#create-the-team] Whoever creates a team workspace is its first Owner. It starts empty: no agents, skills, or memories until you build them or bring them in. Name it and invite people from the team's settings. ## Invite people two ways [#invite-people-two-ways] Enter a person's email, pick the role they'll join with, and **Send invite**. The invite is bound to that address, so it's the right choice when you know exactly who should join and as what. Share one reusable link with a group. Anyone who opens it can join the team, so use it for a known circle and regenerate it if it should stop working. It is separate from an email invite, not a copy of one. Either way, the person joins by opening the invite: they can follow the link or paste the invite code, and they land in the team with the role the invite carried. ## Assign the smallest role that fits [#assign-the-smallest-role-that-fits] Every invite carries a role. Invite most people as **Member**, so they can run the team's agents and read its memories; save **Editor** for whoever maintains shared agents, skills, and context, and **Owner** for whoever is accountable for the team. Roles change later, so start narrow. [Team roles](https://www.hyperagent.com/docs/concepts/teams/members) has the matrix. ## Manage membership as it changes [#manage-membership-as-it-changes] From the same Members settings, an Owner can: Move someone between Member, Editor, and Owner as their responsibility changes, using the role control next to their name. Take a person out of the team. They lose access to the team's agents, skills, and memories; the threads and outputs they already produced stay theirs. Step out of a team you're in. If you're the only Owner, hand ownership to someone else first. One guardrail is worth knowing: a team must always have an Owner, so Hyperagent won't let you demote or remove the last one. To hand a team off, promote another member to Owner first, then step down. Deleting the team entirely is an Owner action and a deliberate one, separate from removing people. ## FAQs [#faqs] An email invite is bound to one address and the role you chose, so it admits exactly that person as exactly that role. The team link is reusable and admits anyone who opens it, which is why it suits a known group and should be regenerated if it leaks. They're independent mechanisms, not two views of the same invite. Member. It lets someone run the team's agents and read its memories without changing the maintained source. Give Editor to the people who maintain shared agents, skills, and memories, and Owner only to those accountable for membership and settings. Roles are easy to change later, so start with the smallest one that fits. No. A team always needs an Owner, so the last one can't be demoted or removed. Promote another member to Owner first, then change or drop your own role. Their access to the team's shared agents, skills, and memories ends, but the threads and outputs they already produced remain theirs. Removing a person is an access decision, not a delete of their work.