Wodex
Back to resources

Why You Shouldn't Share API Keys With Employees: Company Policy and Recovery Blueprint

Sharing raw OpenAI API keys in Slack or local config files breaks cost attribution and offboarding. Copy our 7-clause company AI credential policy, 4-step key rotation SOP, and employee offboarding checklist.

0%
Attribution with a shared key
A shared key cannot show which person or workflow caused each charge
4 high-risk zones
Common leak locations
Team chats, local environment variables, third-party plugins, and Git repositories
Token broker
Controlled alternative
The company gateway holds credentials while employees use revocable work identities
3 documents
Copy-ready templates
A seven-rule policy, a four-step recovery SOP, and an offboarding handover form

Small-business AI credential policy and scattered-key recovery blueprint

AI-CREDENTIAL-POLICY.md
# Company AI tools and model API key policy

## Rule 1: Credential ownership and the approved entry point
All model credits, API keys, and company workspaces purchased by the company are company production assets. Daily work must use the approved controlled workstation and an individual work identity. Never issue a personal copy of a primary API key or allow employees to share one.

## Rule 2: Four places where plaintext keys are prohibited
Do not paste keys into team chats or email, frontend code or public repositories, unapproved browser extensions or desktop plugins, or unprotected personal cloud storage and shared documents.

## Rule 3: Quotas and emergency cutoffs
Every workspace member and test project must have a monthly hard limit and anomaly alerts. Increases above a role limit require approval.

## Rule 4: Classify business data before sending it
Use public material and de-identified customer requests directly. De-identify names, phone numbers, unreleased prices, and long contracts. Never enter bank passwords, production private keys, or unreleased M&A and financial records.

## Rule 5: Human review
A responsible employee must review AI-generated quotes, contract changes, customer promises, and production code before sending or deploying them.

## Rule 6: Report and rotate quickly
Report a suspected exposure within 30 minutes so an administrator can revoke and rotate the key.

## Rule 7: Offboard on the effective date
On transfer or departure, remove the member from the workspace, revoke any isolated test keys, and preserve approved shared Skills in the company library.
Management issueGive employees the API keyWodex workspace identity
Credential copiesOnce posted or entered locally, the company cannot know how many copies existEmployees never see the underlying key and cannot export it
Monthly reconciliationOne shared key produces one opaque billCalls are attributed by member and model
Runaway usageOne script can exhaust the entire keyPer-member limits isolate one person's overuse
Departure dayRotate the key and reconfigure everyoneRemove one member without changing anyone else's setup

Credential isolation and policy boundaries

What it handles

  • Separate employee identity from model credentials so ordinary employees can use capable models without plaintext key exposure
  • Copy and adapt the three templates above for internal policy, recovery, and offboarding workflows

Scope boundaries

  • Production programs that call a model API directly still require a restricted project service key stored in an environment-variable secret vault

End scattered-key use in three days

Publish the seven-rule policy

Make it explicit that new plaintext API keys will not be issued and new personal AI subscriptions will not be reimbursed.

Move the team into one workspace

Use the four-step recovery SOP to bring everyone into the Wodex desktop workstation without interrupting business work.

Revoke old keys and use the handover form

Revoke historical keys in the provider console and give HR and administrators the six-item offboarding checklist.

Frequently asked questions

Is sharing a key through 1Password safe enough?

A password manager protects the transfer, but the key is still exposed once an employee copies it into a local client, browser plugin, or script. That makes individual revocation difficult without rotating the key for everyone.

A key was posted in our company chat but nobody has misused it. Do we still need to rotate it?

Yes. Chat history is copied to multiple devices and backups, and a former employee may retain access. Open the controlled workspace first, then revoke the historical key.

Can administrators see how much each employee uses?

Yes. Individual work identities let the workspace attribute calls and credit consumption by member.

Sources

- OpenAI Help Center: Can I share my API key with my teammate?: OpenAI's guidance against sharing personal API keys.

- OpenAI Help Center: Best practices for API key safety: Guidance on exposure, limits, and rotation.

- OWASP Secrets Management Cheat Sheet: Practical standards for credential lifecycle and revocation.

Related workbenches and blueprints