> ## Documentation Index > Fetch the complete documentation index at: https://docs.frontic.com/llms.txt > Use this file to discover all available pages before exploring further. # Teams A **team** is the top-level container in Frontic — it owns your projects and the resources every project draws on, plus the people working in it and the billing relationship. Most companies have one team; agencies, large groups, and teams running fully separate engagements run more than one. Switching between them is a one-click action in the user menu (top-right). ## What lives at the team level The team is the boundary for several things every project inside it shares. When you're inside a project, these are already there for you to use: The people with access to the team and every project in it. Invited once, available across all projects. See [Members & Roles](/admin/members-and-roles). [Connectors](/connectors/overview) are set up at the team level. Once an integration is connected, every project can pull from its Data Feeds. [Skills, Rules, Commands, and Guides](/context-base/overview) promoted to the team are available in every project. Project-scoped documents stay project-only. One [plan](/admin/billing-and-plans) per team, one invoice. Plan limits and feature gates apply across every project the team owns. Projects, by contrast, hold the stack itself — Data Storages, Blocks, Listings, Pages, project-scoped context documents, and project-level settings. ## When to add another team Most setups don't need a second team — and adding one comes with a real cost: you re-set-up the team-level resources above (members re-invited, integrations re-connected, global context re-authored or re-promoted). The reasons that justify paying that cost: A client engagement that pays its own bill, an internal cost-centre split, an acquisition you haven't merged yet. Different team = different invoice. Two groups of people that shouldn't see each other's projects or integrations. Member access is per-team, so a clean split is the simplest answer. You're an agency running multiple clients in Frontic. One team per client keeps projects, members, integrations, and billing isolated. If you want to **experiment** on something without risking a production project, the right move is a new project inside the same team — not a new team. Same integrations, same members, same context — clean separation at the project level. ## Switching between teams The team picker lives in the user menu (top-right of the admin app). Click your avatar, pick a team, and the admin app switches context — including the project list, the members view, the integrations list, and the billing screen. Your account can belong to as many teams as you've been invited to; teams stay independent (different integrations, different members, different billing) even when you're in both. ## Creating a team A team is created when you sign up — your account starts with one. Adding another team later is done from the same user menu and walks you through name, plan selection, and the first project. ## Related Invite people to the team and pick what they can do. Plan tiers, feature gates, and how billing per team works. Plan limits that apply to every project in the team. Per-project configuration — sits below the team layer.