Skip to main content

Team admin

A developer who also administers one or more teams (TEAM_ADMIN on the team). Everything in the Developer guide applies, plus the workflows below.

Where you work: Everything a developer has, plus Approvals, Spend Governance and Teams in the sidebar's Administration group. FinOps Attribution and Cost Events also appear under Cost management, but only platform admins can open them.

1. Review key requests​

Approvals lists pending requests for your teams (the sidebar badge shows the count). Before approving you can adjust the access group, budget tier, budget, RPM/TPM and expiry. Rejections carry a note back to the requester; approval mints the key in Pending reveal.

2. Manage the team​

On Teams, open your team to add or remove members, promote members to team admin, create applications, and block an application (which blocks its keys).

3. Operate team keys​

You can reveal, rotate, block and revoke keys that belong to your teams — useful when a member leaves or a key leaks. Blocking is instant on the gateway.

4. Watch team spend​

Request Logs include your teams' traffic. FinOps Analytics and Budgets show only your own keys and spend, so use Request Logs for team-wide review. Soft budget alerts (email and in-app, under the bell in the top bar) fire before hard limits block traffic.

Good to know​

  • You cannot raise your team's budget — ask an org or platform admin.
  • You cannot create new teams; that is an org or platform admin task.