> ## Content Index
> Fetch the complete content index at: https://serpapi.com/blog/llms.txt
> Use this file to discover other available public pages before exploring further.

# Team Management feature: One Account, Multiple People, Zero Chaos
- URL: https://serpapi.com/blog/team-management-feature-one-account-multiple-people-zero-chaos/
- Published: 2026-01-09T00:07:33.000Z
- Updated: 2026-01-09T00:20:58.000Z
- Description: Manage your SerpApi - Search API account with our team management feature.
- Author: Hilman Ramadhan
- Tags: Tips&Tricks

If you’re using SerpApi with more than one person (or more than one environment), the “one shared API key” approach gets messy fast.

- Someone rotates a key and breaks production.
- Finance needs invoices, but you don’t want to share your login.
- You want to track usage by project, but everything is mixed together.

That’s why we launched the [Team Management](https://serpapi.com/team-management) feature: it helps you invite teammates, separate access, and keep visibility—without turning account management into a full-time job.

![](https://storage.ghost.io/c/a5/00/a5004977-0dd2-4bcd-9292-dd0e05d4c59e/content/images/2026/01/CleanShot-2026-01-09-at-07.51.37.png)

Team Management feature in SerpApi

> Once you're logged in, you can access our [team feature page](https://serpapi.com/team-members).

## What can you do

### 1) Use multiple API keys (per person or per environment)

Instead of one key for everyone, you can generate **unique API keys** for each team member or even for each environment (like `dev`, `staging`, `prod`). That keeps things cleaner and safer.

### 2) Share one account (plans + billing stay in one place)

Your team can collaborate under a single shared account—so searches, plans, and billing don’t end up scattered across separate personal accounts. 

### 3) Monitor usage by team member

When each person (or environment) has their own API key, you can see usage more clearly and track performance metrics like response times.

### 4) Transfer ownership when roles change

When someone leaves the company or switches responsibilities, you can **transfer ownership** to another team member, so the account doesn’t get stuck with one person forever.

## Roles: give the right access to the right people

Team Management is easier when people only see (and control) what they need. Here are the roles available:

### **Admin**

Full access to everything, including managing other team members.

**Best for:** team owners, engineering leads, whoever manages account settings.

### **Developer**

Use APIs and view their own search statistics.

**Best for:** engineers building and testing integrations.

### **Billing**

Manage subscription and payment methods.

**Best for:** finance/ops teammates who handle invoices and payments.

### **Viewer**

Read-only access to billing info, team members, and searches.

**Best for:** stakeholders who need visibility but shouldn’t change anything.

## Common setups (simple and practical)

### Setup A: One product team

- Admin: Engineering lead
- Developers: Engineers
- Billing: Finance
- Viewer: PM or founder

### Setup B: Multiple environments 

- Create separate API keys for `dev`, `staging`, and `prod`
- Give developers access to `dev/staging`
- Keep `prod` tightly controlled (admin-owned)

### Setup C: Agency/client work

- One team account
- Separate keys per client/project\*
- Viewer role for clients who want transparency  
    
\*At the moment, all team members will use the same credits resource, so you need to create another layer to distribute or control the credit for each clients.

I hope it helps. Just let us know if your team has any other needs! Please reach out to contact@serpapi.com