"Hey, can you help me set up my OpenAI key?"
It's the third time this week. New team member joins, needs AI summaries, doesn't have a key. Now you're walking them through OpenAI's console, explaining billing, and hoping they don't accidentally create a key with no spending limits.
Multiply that by every person on your team. Then multiply it again when someone leaves and you realize their key was still active. Or when someone's key hits rate limits because they picked the wrong tier.
Managing individual API keys is like managing individual VPN configs. It works until it doesn't. And then it's your problem.
The Old Way (Death by a Thousand Keys)
Every team member needed their own OpenAI API key. That meant:
- Onboarding friction - New hire can't use AI features until they set up billing with OpenAI
- Zero visibility - Who's using how much? No idea. Hope nobody's running up a bill
- Offboarding gaps - Did we revoke their key? Is it still active somewhere?
- Support overhead - "My API key stopped working" becomes your ticket
For a team of five, maybe manageable. For a team of fifteen? You've just created an API key management job for yourself.
The New Way: One Key, Done
Team owners and admins can now configure a shared OpenAI API key for the entire team.
Set it once. Everyone gets AI features. No more key distribution. No more onboarding friction. No more "can you help me set this up" messages.
How to Set It Up
- Go to Team in the sidebar
- Select the AI Config tab
- Enter your OpenAI API key
- Click Save
Thirty seconds. Your entire team now has AI-powered summaries.
Finally, Visibility
The AI Config tab shows you what's actually happening:
- Total cost across the team
- Number of summaries generated
- Tokens used (for the curious)
- Per-member breakdown - see who's using what
No more mystery bills. No more "who ran 500 summaries last month?" You'll know.
This is the kind of visibility you wish you had for every SaaS tool your team uses.
Pick Your Model
Choose between:
| Model | Best For | Cost |
|---|---|---|
| GPT-4o-mini | Most summaries - fast, accurate, cheap | Low |
| GPT-4o | Complex analysis when you need depth | Higher |
The model applies team-wide. Start with GPT-4o-mini - it handles 95% of use cases at a fraction of the cost. Switch to GPT-4o when you need the extra firepower.
Security (Because You're About to Ask)
Your API key is sensitive. We treat it that way:
- Encrypted at rest using AES-256-GCM (same as your connector credentials)
- Masked in the UI after saving - even admins can't see it again
- Admin-only access - regular members use AI features but never see the key
- Audit logged - key changes are tracked
Regular team members see "AI Enabled" and can use summaries. They never see, access, or need to think about the key itself.
The Math
Let's say you have 10 team members:
Old way:
- 10 individual OpenAI accounts to set up
- 10 billing configurations to manage
- 10 keys to track and eventually revoke
- Unknown total spend across all accounts
New way:
- 1 key to manage
- 1 place to see all usage
- 1 bill to track
- Complete visibility into team consumption
It's not revolutionary. It's just how it should have worked from the start.
Set It Up Today
Go to Team settings, add your API key, and stop managing individual keys.
Your team gets AI summaries. You get your sanity back.
Because "can you help me set up my API key" shouldn't be a recurring meeting.
Enjoyed this post?
Subscribe to get new posts and product updates delivered to your inbox.