On an Enterprise plan, a tight team-wide spend limit is set while several members already carry a more generous group override. Which limit governs those members?

The principle — Spend limits can reach the same person from several places at once: a team-wide default, a group override, and a member override. When more than one applies, Cursor resolves the conflict by applying the highest applicable limit.

Why the key is correct — The more generous override wins, so those members keep spending past the tight team figure until their own limit is reached. This has a second edge worth knowing: lowering the team-level limit does not pull anyone with an existing override back down, because the team figure is only the default for people who have no override at all. To bring a member under the team number, the override has to be cleared, not undercut. An admin who assumes otherwise sets a tight limit, believes the team is capped, and still receives the larger bill.

Why the others are wrong — Assuming the most restrictive limit wins is a straight transfer from permission systems, where narrowing access on conflict is the safe default; spending resolves in the opposite direction. Assuming the team level supersedes overrides inverts their purpose, since an override exists to depart from the default. Recency plays no part either: these are separate settings evaluated together rather than one field being overwritten, so the newest edit does not automatically govern.

Remember this — Highest applicable limit wins, and lowering the team default leaves overrides untouched. Clear the override to actually cap someone.

Sources — Cursor's spend limits documentation.