---
title: "Organization"
description: "Manage a Shiplight Cloud organization — roles, inviting and removing members, organization settings, and switching between organizations."
---

# Organization

<div class="view-markdown-wrapper">
<ViewMarkdown />
</div>

An organization owns everything in Shiplight Cloud: test results, CI runners, API tokens, and billing. Your account is a member of one or more organizations, and everything you see in the app belongs to whichever one is currently active.

Manage yours under **Settings** at [app.shiplight.ai/settings](https://app.shiplight.ai/settings).

## Roles

There are exactly two roles: **owner** and **member**.

|                                              | Member | Owner |
| -------------------------------------------- | ------ | ----- |
| View runs, tests, and analytics              | ✓      | ✓     |
| View organization usage                      | ✓      | ✓     |
| Create personal API tokens                   | ✓      | ✓     |
| Invite, remove, and promote members          |        | ✓     |
| Rename the organization, change its logo     |        | ✓     |
| Manage billing, plans, top-ups, and invoices |        | ✓     |
| Connect GitHub and manage repositories       |        | ✓     |
| Enable CI runners and edit runner pools      |        | ✓     |
| Create and revoke organization API tokens    |        | ✓     |

Members who open an owner-only page are redirected to the dashboard rather than shown an error.

Roles are evaluated live. Changing someone's role — or removing them — takes effect immediately, including for API tokens they created.

## Members

Owners manage the roster at [app.shiplight.ai/settings/members](https://app.shiplight.ai/settings/members). Invitations expire after **7 days**, and membership is created only once the invitee explicitly accepts — a sent invitation is not yet a member.

::: warning Work email addresses only
Invitations to personal email domains (Gmail, Outlook, and similar) are rejected with _"Work email required"_. This applies at sign-up too.
:::

Two things the interface doesn't tell you:

- **The last owner cannot be removed.** Promote someone else first.
- **There is no demote action.** Promoting someone creates a co-owner without demoting you, but turning an owner back into a member means removing and re-inviting them.

Removed members become inactive rather than deleted, and can be reactivated later.

## Organization settings

[app.shiplight.ai/settings/general](https://app.shiplight.ai/settings/general) holds the organization's name and logo, both editable by owners.

**Region** is your data residency — United States or European Union. It is fixed when the organization is created, so contact Shiplight if you need it changed.

Everything else has its own page under Settings. [Members](https://app.shiplight.ai/settings/members), [Subscriptions](https://app.shiplight.ai/settings/subscriptions), [Billing](/cloud_v2/billing), [Invoices](https://app.shiplight.ai/settings/invoices), and [Integrations](https://app.shiplight.ai/settings/integrations) are owner-only; Profile is your own.

### Integrations

Connecting GitHub is a prerequisite for [CI Runners](/cloud_v2/ci-runners): until the Shiplight GitHub App is installed and the repository appears as an active connected repo, jobs are never dispatched and sit queued in GitHub. It also fills in the commit, branch, PR, and author metadata on your [runs](/cloud_v2/test-results), along with the links back to GitHub.

Only owners can install the App or change which repositories it covers. See [CI Runners → Setup](/cloud_v2/ci-runners#setup) for the permissions it requests and the constraints worth knowing before you start.

## Related

- [Billing](/cloud_v2/billing) — plans, usage, and invoices
- [API Tokens](/cloud_v2/api-tokens) — personal versus organization tokens
- [CI Runners](/cloud_v2/ci-runners) — connecting GitHub and enabling runners