Each team's keys, members, inherited policy, and usage in one workspace.
Teams
Mapped
Keys
Owned
Settings
Inherited
Support
3 keys
Customer-facing AI workflows.
Engineering
2 keys
Coding agents and internal tools.
Finance
Read view
Spend review by owner.
New capabilities
Group members around products, functions, or AI workflows, so spend and access line up with how the company actually works.
Give each team its own keys and usage views, so a team sees its own spend and logs without exposing everyone else's.
Set model access, logging, ZDR, and limits at the team level and let keys inherit them, instead of configuring each key by hand.
Who Concentrate is designed for
A team workspace groups the people, keys, settings, and usage for one part of the org. Support sees support spend; engineering sees engineering keys — without a shared provider secret or one global dashboard everyone interprets differently.
Own keys and settings for your apps while inheriting org-wide policy you should not relax.
Review spend by team before chargeback or renewal conversations.
Enforce model access, logging, and ZDR at team scope so new keys pick up the right defaults.
Organization policy can prevent a child key from weakening limits or retention the security team set.
Feature basics