# Summary This issue outlines the user flows for the teams proof of concept. It includes two major foundational components. 1. **Team management** - creating teams, inviting members, and editing permissions within the team environment. 2. **Resource collaboration** - users can invite teams to resources through a modal interface at the group and project level. [Figma prototype](https://www.figma.com/proto/oHJOTN3XZpLIBXe7YuDQmj/Teams-Concept?page-id=513%3A7492&node-id=520-8550&p=f&viewport=224%2C311%2C0.08&t=k8FTJanDnBNCPzW0-1&scaling=scale-down&content-scaling=fixed&starting-point-node-id=520%3A8550&show-proto-sidebar=1) # User flows **Creating a team & adding members** 1. Go to the Teams homepage 2. Click "**Create a new team**," complete the required fields, and click "**Confirm**" 3. User will be redirected to the new team's detail page 4. Click "**Invite member**," set member permissions, and click "**Confirm**" 5. Team creation complete **Assigning teams to Groups/Projects** 1. Navigate to target group or project 2. In the members section, click "Invite by Team" 3. A team selection modal will appear 4. Select the desired team, then configure permissions: * **Option 1:** Set a maximum role limit that applies to all team members * **Option 2:** Assign the same role to all team members 5. Invitation complete # **Users roles** **Team Owner** * Create new teams * Invite members to join the team * Remove members from the team * Modify member roles * Accept invitations to access groups or projects **Team Member** * Accept invitations to join teams * Can request to join existing teams * Request to access groups or projects on behalf of the team ## Invite team modal - warning system **Permission Conflicts** * Permission escalation: Team member would receive higher permissions than currently assigned * Permission downgrade: Team member would lose existing permissions **Membership Overlap** * Duplicate membership: Team members already belong to the target group/project