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:Members
The people with access to the team and every project in it. Invited
once, available across all projects. See Members & Roles.
Integrations & Data Feeds
Connectors are set up at the team level.
Once an integration is connected, every project can pull from
its Data Feeds.
Global Context Base documents
Skills, Rules, Commands, and Guides
promoted to the team are available in every project. Project-scoped
documents stay project-only.
Plan & billing
One plan per team, one invoice. Plan
limits and feature gates apply across every project the team owns.
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:Genuinely separate billing
A client engagement that pays its own bill, an internal cost-centre
split, an acquisition you haven’t merged yet. Different team =
different invoice.
Disjoint membership
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.
Agency-style multitenancy
You’re an agency running multiple clients in Frontic. One team per
client keeps projects, members, integrations, and billing isolated.
Switching between teams
The first item in the breadcrumb at the top of every page is the active project. Once you have more than one project, click it to open the project switcher: your projects are grouped by team, with the current team first. Each team shows its square avatar and each project its round avatar, with a dot that marks the project active or inactive. The current project is marked with a check, and Create Project at the bottom opens the new-project dialog. Pick a project in another team and the admin app switches context - including the project list, the members view, the integrations list, and the billing screen. A team appears there once it has at least one project. The user menu (click your avatar, top-right) shows the team you’re currently working in, with its avatar and name, above your own name. It has no team list. 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.Team avatar
Each team has a square avatar. It shows in the user menu and in the project switcher. Until you upload an image, the avatar shows the team’s initials on a colored square; the color is derived from the team, so it stays the same for everyone and across sessions. To set it, open the user menu (top-right) and click the team name at the top. In the Team avatar dialog, drop an image or click to choose one (PNG, JPEG, or WebP, up to 5 MB), crop it to the square, and click Save. Remove clears the image and brings back the initials.Creating a team
A team is created when you sign up - your account starts with one. You can add another team at any time from the user menu:1
Open the user menu
Click your avatar (top-right) and choose Create new Team.
2
Name the team and pick a plan
Enter the team name, choose a plan, and accept the terms.
3
Create the first project
The admin app signs you into the new team, with you as its Owner. Because the team has no projects yet, it opens project setup so you can create the first one.
Related
Members & Roles
Invite people to the team and pick what they can do.
Billing & Plans
Plan tiers, feature gates, and how billing per team works.
Limits & Quotas
Plan limits that apply to every project in the team.
Project Settings
Per-project configuration - sits below the team layer.