# Developer Accounts

> One admin user per developer in API Maker - own user path, own secrets, own branch, same Git repository - created by the root user on the Accounts page or through the management API.

Source: https://docs.apimaker.dev/v1/docs/dev-accounts/dev-accounts.html

A team works on one project with one admin user per developer. Each developer signs in to the admin panel with their own account, pulls the shared branch, works, and pushes. The APIs of each account answer under its own user path.

| | |
|---|---|
| Who creates them | The root user, on the Accounts page : name, email, API path, password, active. **Clone** copies one. |
| Unique | The API path and the email. |
| Own to each account | Its secrets, its Git branch and credentials, its masked database names, its sandbox processes, its Redis cache. |
| Shared | The Git repository, and through it every item of the project. |
| From a script | The [management API](https://docs.apimaker.dev/v1/docs/am-resources/operate-api-maker-using-api.html) creates, updates and deletes admin users. |

## A developer joins

1. The root user creates the account and gives the credentials.
2. The developer sets the Git URL and commit email in their **User info**, pulls the branch of the team, and adds the connection strings and keys of their own databases to their secret.
3. When the database names of their machine differ from the ones in the code, they [mask](https://docs.apimaker.dev/v1/docs/features/mask-database.html) them.
4. They work under `/api/…/<their path>/…`, test with their own API users, and push to a branch of their own for a pull request.

## Related

- [Git integration](https://docs.apimaker.dev/v1/docs/Git/git.html) · [Mask database names](https://docs.apimaker.dev/v1/docs/features/mask-database.html) · [Secrets](https://docs.apimaker.dev/v1/docs/secrets/secrets.html)