> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/integrations/integrating-perkville/developer-admin-access-for-perkville-integrations.md).

# Developer admin access for Perkville integrations

When a business uses Perkville and wants a developer or integration partner to connect an app to its Perkville account, the developer needs admin access to that business’s Perkville account.

A Perkville admin at the business [must invite an email address from the developer](https://docs.perkville.com/features/settings/staff-members) as an admin on the business’s Perkville account.

### Who should complete this step

A [current admin on the business’s Perkville account](https://docs.perkville.com/features/settings/staff-members) should complete this setup. The developer cannot grant this access to themselves.

### Choose the email address to invite

Before adding the developer as an admin, confirm which email address the developer wants to use.

The email address can be either:

1. A real person’s work email address at the developer, such as `name@developercompany.com`.
2. A shared or integration-specific email address, such as `perkville_businessname@developercompany.com`.

Some developers prefer to use an integration-specific email address so the integration is not tied to one employee’s account. This can help avoid access issues if that employee leaves the developer’s company.

### Add the developer as an admin

The instructions for adding the developer's email to your account can be found [here](https://docs.perkville.com/features/settings/staff-members).

### Troubleshooting

#### The developer did not receive the invitation

Ask the developer to check the inbox and spam folder for the invited email address. Confirm that the email address was entered correctly. If needed, remove the pending invitation and send a new one.

#### The developer’s employee left the company

If the developer used an individual employee’s email address, remove that admin from the Perkville account and invite a new email address provided by the developer.

#### The developer needs access for multiple business accounts

Admin access must be granted separately for each Perkville business account that the developer needs to integrate with.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.perkville.com/integrations/integrating-perkville/developer-admin-access-for-perkville-integrations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
