Organizations, Teams and Groups
Enterprise Organizations sit above teams; groups cut across membership and permissions.
Use the right surface
After this you can pick Enterprise Organizations for the right job and define done.
Done means you can draw the org -> team -> group model and explain effective settings.
Enterprise rollout work needs identity, controls, privacy and usage evidence in one operating view.
Use Enterprise Organizations when a large company needs one admin plane across multiple departments or business units. Keep the boundary narrow.
Start small. Name the job, attach the context that proves the point and decide what evidence would make the output trustworthy.
Read the loop before touching the controls. The first beat frames the work, the second uses Cursor, the third checks the result and the fourth leaves a handoff someone else can inspect.
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
Run this loop in a real repo.
- Entry point
- Organizations docs and org/team dashboard
- Source
- Organizations docs, June 3, 2026 changelog and Organizations blog
Use the source as the product reference.
Ask Cursor for an output you can inspect.
If the output cannot be checked, narrow the task before you continue.
A good run leaves a file, setting, screenshot, command result or written claim you can verify.
Takeaway. Done means you can draw the org -> team -> group model and explain effective settings.
Self-check
QWhen should you reach for Enterprise Organizations?
Run it
After this you can do the task with clear scope and one proof point.
Treat this as a short practice loop, not a product tour. The task should be small enough that you can inspect the result without trusting the summary.
- 1Map business units or departments to teams.
- 2Use groups for cross-team model access, spend or agent permissions.
- 3Explain org-level identity, usage rollups and team-specific governance.
- 4Check effective settings where most permissive wins.
The exercise is complete only when the proof matches the requested outcome. If the proof is weak, reduce the scope or fix the context instead of adding more instructions.
Keep the task small enough to review.
Effective permissions are calculated correctly.
Takeaway. Stop when you have proof: Team and group membership are not conflated..
Self-check
QWhich habit makes this workflow safe to use on a real project?
Check it
After this you can find the first failed check before changing tools.
Verification decides the next move.
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
Pick a row to see what to look for.
Use the first failure signal as the next prompt. Broad retries usually make the run noisier; a narrow retry gives Cursor a concrete repair target.
No proof means more checking.
Use a real repo or admin setting. Save the prompt, context and proof.
Takeaway. If it fails, find the first failed check.
Self-check
QThe workflow failed. What is the best first move?