How to Manage and Optimize Claude AI Company Settings for Teams

When your organization adopts Claude AI, managing access, usage, and security at the company level becomes essential. The Anthropic Console provides a centralized dashboard for configuring company settings that affect all team members and API integrations. This guide walks you through the key settings, best practices, and actionable steps to keep your Claude deployment secure and cost-effective.

Understanding the Company Settings Dashboard

The Company settings section in the Anthropic Console (accessible at console.anthropic.com) is your command center for organizational control. Here you can:

• Manage API keys for different teams or projects
• Set usage limits and spending caps
• Monitor real-time and historical API usage
• Control model access (e.g., Claude 3 Opus vs. Sonnet)
• Add or remove team members

Access these settings by logging into the Anthropic Console, clicking your profile icon, and selecting Company Settings.

Configuring API Keys for Teams

API keys are the primary way your applications authenticate with Claude. For security, never hard-code keys in your source code. Instead, use environment variables or a secrets manager.

Creating and Managing API Keys

• Navigate to API Keys under Company Settings.
• Click Create Key and give it a descriptive name (e.g., "Production Backend" or "Dev Testing").
• Copy the key immediately — it will not be shown again.
• Assign the key to a specific workspace or leave it as organization-wide.

Best practice: Create separate keys for development, staging, and production environments. This makes it easier to revoke access if a key is compromised without affecting other systems.

Using API Keys in Code

Here’s how to securely use your API key in Python:

import os
from anthropic import Anthropic
Load from environment variable (recommended)
client = Anthropic(api_key=os.environ.get("ANTHROPIC_API_KEY"))
Example: Send a message
response = client.messages.create(
    model="claude-3-opus-20240229",
    max_tokens=1024,
    messages=[
        {"role": "user", "content": "Hello, Claude!"}
    ]
)
print(response.content)

For TypeScript/Node.js:

import Anthropic from '@anthropic-ai/sdk';
const client = new Anthropic({
  apiKey: process.env.ANTHROPIC_API_KEY,
});
async function main() {
  const response = await client.messages.create({
    model: 'claude-3-opus-20240229',
    max_tokens: 1024,
    messages: [{ role: 'user', content: 'Hello, Claude!' }],
  });
  console.log(response.content);
}
main();

Setting Usage Limits and Spending Caps

Uncontrolled API usage can lead to unexpected bills. The Company Settings page lets you set both hard and soft limits.

Configuring Spending Limits

• Go to Usage & Billing in Company Settings.
• Under Spending Limits, set a monthly cap (e.g., $500).
• Optionally, set an alert threshold (e.g., 80% of the cap) to receive email notifications.
• Choose whether to Hard Stop (block requests once the cap is reached) or Soft Warn (continue but notify admins).

Pro tip: Start with a soft warning for the first month to understand your team’s usage patterns, then switch to a hard stop once you have a baseline.

Monitoring Usage in Real Time

The Usage dashboard shows:

• Total tokens consumed (input + output)
• Cost breakdown by model (Opus, Sonnet, Haiku)
• Requests per minute/hour
• Error rates (rate limits, authentication failures)

Use the Export button to download CSV reports for accounting or internal chargebacks.

Managing Team Access and Roles

If you have multiple team members who need access to the Anthropic Console (not just the API), you can manage their permissions from Company Settings.

Adding Team Members

• Click Team in the left sidebar.
• Click Invite Member.
• Enter their email address and select a role:

- Admin: Full access to all settings, billing, and API keys - Developer: Can view usage and create API keys, but cannot change billing or delete keys - Viewer: Read-only access to usage and settings

• Click Send Invite. The user will receive an email with a link to join.

Revoking Access

If a team member leaves or changes roles, immediately revoke their access:

• Go to Team settings.
• Find the user and click the three-dot menu.
• Select Remove Member.
• Also revoke any API keys they created (under API Keys).

Optimizing Model Access for Cost Efficiency

Not every task requires Claude 3 Opus. You can restrict which models your team can use from Company Settings.

Setting Model Access

• Go to Models under Company Settings.
• Toggle which models are available:

- Claude 3 Opus: Best for complex reasoning, code generation, and analysis - Claude 3 Sonnet: Good balance of speed and capability for most tasks - Claude 3 Haiku: Fastest and cheapest, ideal for simple queries and high-volume tasks

• Optionally, set a default model for new API keys.

Recommendation: Enable all models but set Sonnet as the default. Require explicit model selection for Opus to prevent accidental overuse.

Security Best Practices

• Rotate API keys regularly — every 90 days is a good cadence.
• Use IP whitelisting if your team works from fixed IP addresses.
• Enable audit logging to track who created or deleted keys.
• Never share API keys in emails, chat, or public repositories.
• Use environment variables or a secrets manager like AWS Secrets Manager or HashiCorp Vault.

Troubleshooting Common Issues

"API key not found" error

This usually means the key is invalid or has been revoked. Check the API Keys page in Company Settings to verify the key is active. If you recently rotated keys, update your environment variables.

Rate limit exceeded

Claude API has rate limits based on your plan. In Company Settings, you can view your current rate limits under Usage. To increase limits, contact Anthropic support or upgrade your plan.

Unexpected high costs

Check the Usage dashboard for spikes. Common causes include:

• A developer accidentally using Opus instead of Sonnet
• A loop in your code that sends repeated requests
• A new integration that is more chatty than expected

Set up alerts in Usage & Billing to catch these early.

Key Takeaways

• Centralize API key management in the Anthropic Console, using separate keys for each environment to limit blast radius.
• Set spending caps and alerts to prevent surprise bills — start with soft warnings, then enforce hard stops.
• Assign roles carefully — give Admin only to those who need billing access, and use Developer or Viewer roles for everyone else.
• Restrict expensive models like Opus to specific use cases, and default to Sonnet or Haiku for routine tasks.
• Monitor usage regularly and rotate API keys every 90 days to maintain security and cost control.