Teams and limits

Group people into teams and cap what each team can spend, without touching anyone's personal balance.

A team is a named sub-group inside a workspace — Marketing, Design, the agency working on one client. Teams do two jobs: they organize the roster, and they give you a place to put a spending limit that applies to several people at once instead of one at a time.

Teams live in Settings → Governance → Teams, described there as "Group members into teams, set a spending limit for each, and see how they spend."

This page is the exception in the Governance section. Every other page there opens for anyone who can view workspace activity and governance — Teams needs the permission to change workspace settings instead, not in addition. In practice that means an admin. See Roles and permissions.

One person, one team

Someone belongs to one team at a time, or to none. Assigning a person to a second team moves them; it doesn't add them. That's what makes a team limit unambiguous — there's never a question of which team's cap applies to you.

People who aren't on any team are still full members of the workspace. They draw from the workspace pool like everyone else, and they're listed under the Unassigned tab so they don't quietly go unnoticed: "New members will appear here until you assign them." Once nobody is left, that tab reads "Everyone is in a team".

What the page shows you

Four tiles across the top answer the questions an admin actually asks:

Teams and In a team

How many teams exist, and how many of your members are on one. The second tile names how many are still unassigned.

Credits used

What the teams have spent this cycle. With no caps set anywhere it says so rather than showing a meaningless percentage.

Near or over limit

How many teams have reached 80% or more of their cap — the early warning before anybody is actually blocked.

Below that, two tabs — "All teams" and "Unassigned" — each with their own search, and a row per team showing its members and its spending against its limit.

Creating a team

Press "Create team"

Top right. The dialog is headed "Create team": "Create a new team to organize members and set spending limits." It has two tabs, "Details" and "Members".

Name it and give it a color

"Team name" is the only required field — the placeholder suggests something like a department name. "Team color" is what identifies the team at a glance elsewhere in the product, and "Description (optional)" answers "What is this team responsible for?"

Set a spending limit, or don't

"Spending limit (optional)" is the cap in credits for a billing cycle. The field explains the rule underneath it: "Leave empty for no limit. Members inherit team limit if they don't have a personal one."

A team with no limit is a perfectly good team — it's just an organizational grouping, and its members draw from the workspace pool.

Add people

The "Members" tab lists everyone available to add and everyone already on the team. Changes are staged and summarized — how many to add, how many to remove — before you save.

Editing works the same way: open a team's menu and choose "Edit team".

Who can do what to a team

This is the one thing about teams that surprises people, so it's worth being explicit. Creating, renaming, deleting a team and setting its limit are workspace settings. Putting a person on a team or taking them off is member management. They're two different permissions.

Because of that split, someone can be able to assign people to teams without being able to open the Teams page at all. Assignment is also available from a person's own profile in the member directory, which isn't part of Governance — so a person who manages members reaches it there, changes somebody's team, and still can't create the team they're assigning into. Today, only an admin holds both permissions.

Deleting a team

The team's menu has "Delete team", and the confirmation is blunt about what happens: "This permanently deletes the team and its spending limits. Members stay in the workspace. This can't be undone."

Nobody loses their account, their work, or their place in the workspace. What they lose is the team's cap — so anyone who was relying on it falls through to the next rule below.

Spending limits: three levels, first match wins

A team limit is one of three ways the credits you can spend get decided, and Endless stops at the first rule that applies to you.

Your personal limit

If someone set a spending limit on your membership, that is your ceiling. It's set per person in Settings → Members, and the default is "Unlimited".

Your team's limit

No personal limit? Then your active team's limit applies, if it has one.

The workspace pool

No personal limit and no team limit means you draw straight from the workspace balance, like everyone else.

First match wins, and only the first. A personal limit doesn't add to a team limit — it replaces it. Give someone a personal limit and their team's cap stops applying to them entirely. Credits and spending is the full picture, including what a refill does and doesn't reset.

Someone who runs into the team's cap is told which wall they hit: "This team reached its spending limit. Your workspace still has credits." That's the message to expect in a support question — it means the team's number needs raising, not the workspace's.

Seeing where a team's credits went

Open a team from the list and you get its own page: its properties, its members, its spending against the cap as a percentage, and its recent activity — the credit movements attributed to its people, with a line per transaction. When a team has spent nothing yet it says so plainly.

A limit is a ceiling, not a budget you have to spend, and it doesn't reserve anything. Two teams can each have a generous cap while the workspace itself runs out first — the pool is shared, and a team limit never guarantees credits are waiting for it.

Teams are also a governance scope

Once a team exists, it becomes a target you can point other governance at. Both the models page and the features page let you pick Workspace, a Team, or a Person as the scope, so a team is the natural unit for "contractors get a smaller catalog" or "this group doesn't need video".