Skip to lesson
Exit
Teams Dashboard Settings Map1 / 2

2 min lesson

The case: you can map the dashboard by job, not by memorized menu order

Explain the practical point behind "You can map the dashboard by job, not by memorized menu order."

Step 1 of 2

The case: you can map the dashboard by job, not by memorized menu order. Start with this check: The setting location matches the admin job. Walk it once against a real situation so you can defend the call, not just assert it.

Map Overview, Members, then Billing

0:39 · narrated
Read this demo as text
  1. cursor.com slash dashboard is the Teams map. Overview shows credits, the setup checklist, and AI Share versus Agent Edits — know the shape before you invite more seats.
  2. Members is the invite and role job. Who can spend team credits lives here — not in desktop Settings.
  3. Billing and Invoices covers the Team plan. SSO and SCIM stay behind Explore Enterprise — that banner is a plan gate, not an identity dashboard to invent.
Walk Overview → Members → Billing on cursor.com/dashboard — SSO and SCIM stay behind Explore Enterprise.

Practice next: Open your Teams dashboard and name which job lives on Overview, Members, and Billing before you change seats.

Simulated Cursor 3.12 (macOS, light) — beta educational reconstruction, not the real product.

Learn more

Full explanation

Admin control plane

Teams dashboard — map three admin jobs to where they live
Admin control plane
SayAn admin asks me three 'where do I…' questions. I answer each by the job, not by scrolling the menus, and I say how strong the control actually is.
SayJob one: distribute one MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. server to the whole team.
DoGo to Dashboard → Integrations & MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition.. Set the Team MCP server up once there; it is then made available through a team marketplace.
SeeLocation matches the job, and this is a deterministic control: configured once, distributed to the team.
SayJob two: manage what our team shares internally.
DoGo to Dashboard → Plugins → Team Marketplaces. That is where team marketplaces are configured.
SeeRight section for the job. The control steers what is shared; it does not enforce behavior.
SayJob three: see how the team is actually using Cursor.
DoOpen the Admin Dashboard for usage information and key metrics.
SeeThis is observability only. Usage analytics show behavior; they do not control it, so I never sell them as enforcement.
DoFlag the plan gate before the admin goes looking: audit logs and service accounts are Enterprise, not Teams.
SeeNaming the Enterprise gate keeps me from teaching a control this team does not have.
SeeEvery answer went from the admin job to the dashboard section that owns it, with control strength named. The proof point: the setting location matches the job, on the right plan.
Learn more

Optional practice

You can map the dashboard by job, not by memorized menu order

QYou've applied it. What actually proves the work is done, not just a plausible answer?