---
title: "Organization"
description: "Manage team members, choose your service region, and find the CLI and AiSM keys used for third-party integration."
---
> For the complete documentation index, see [llms.txt](/llms.txt).

import { Aside, Steps } from '@astrojs/starlight/components';

**Organization** is a top-level section in the Developer Console's left navigation, separate from Settings. It has three tabs: [Members](#members), [Service Region](#service-region), and [Third Party](#third-party).

## Members

DoveRunner supports organization accounts, where several people share one account for sealing, dashboards, and real-time streaming. Billing is consolidated on the administrative account, so team members do not need to register their own payment details.

The **Team Management** table lists everyone with access:

| Column | Description |
| :----- | :---------- |
| **User Name** | The member's display name, if they have set one. |
| **Email Address** | The account the member signs in with. |
| **Notes** | Free-text note, useful for recording a member's role or that they have left. |
| **Joining Date** | When the member joined the organization. |

Use the search box to find a member by name or ID.

### Inviting a Member

<Steps>

1. Click **ADD** to open the **Invite Team Member** dialog.

2. Enter the **Team Member Email Address**.

3. Click **INVITE**.

</Steps>

The dialog also lists previous invitations with their **ID**, **Invitation Date**, and **State**, so you can confirm whether an invite was already sent.

<Aside type="caution">
Everyone in the group can access your applications and their data. Invite only people who should see that.
</Aside>

Invited people receive a confirmation email. A new user follows the normal sign-up flow from the link; an existing DoveRunner user cannot be merged into your group from the console — raise a ticket with the [Help Center](https://support.doverunner.com/) to have it done.

## Service Region

Determines where your sealed builds, console data, and account information are processed.

| Region | Notes |
| :----- | :---- |
| **Global** | The default for all accounts. |
| **Mumbai** | Hosted to support data localization requirements. |
| **Jakarta** | Hosted to support data localization requirements. |

<Aside type="note">
Changing the region requires an authorized account. Contact the [Help Center](https://support.doverunner.com/) if you need to use a local region for data localization compliance.
</Aside>

## Third Party

Holds the download and the keys used to integrate DoveRunner with your own tooling.

### CLI Tool for Android AppSealing

**DOWNLOAD** provides the CLI jar used to seal Android apps from a build pipeline, and the page shows your **CLI Key** — the value passed as `-authkey` when you run it.

DoveRunner reports the CLI as tested against Jenkins, Bitbucket Pipeline, Fastlane, AWS CodePipeline, TeamCity, and Circle CI.

See [Basic Configuration](../android/cicd/basic-configuration/) for the command-line options.

<Aside type="caution">
The CLI Key authenticates sealing requests for your account. Treat it as a secret — store it in your CI system's secret store rather than committing it to a repository.
</Aside>

### AppSealing Data API

Gives programmatic access to hacking statistics and hacker device IDs for your own dashboards or SIEM. Access is not enabled by default — contact the [Help Center](https://support.doverunner.com/) to request it.

### AiSM Key

Required for iOS integration through AiSM. Enter it in the AiSM authentication window. Like the CLI Key, treat it as a secret.