Organization
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.
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 | ✓ | |
| Reactivate inactive members | ✓ | |
| Configure Enterprise SSO and SCIM | ✓ | |
| 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.
Members
Owners manage the roster at Settings → Members, with Active, Invited, and Inactive views.
Joining an organization
Employees can join in two ways:
- Invitation: an owner invites them and they accept. Invitations expire after 7 days; a pending invitation does not grant membership.
- Enterprise SSO: eligible employees join as members on their first successful company sign-in, without a separate invitation. See Enterprise SSO for verified-domain and account requirements.
Both paths are subject to the organization's member limit.
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.
Changing a member's role
To make a member an owner, open their action menu and select Promote to owner. This creates a co-owner and preserves your own role.
There is no demote action. To change an owner back to a member, another owner must remove them and invite them again with the member role. Role changes also affect the permissions of that person's personal API tokens.
Removing members
To remove someone, open their action menu and select Remove member. The last owner cannot be removed; promote another member to owner first. Connected organizations can also automate removal of ordinary members with SCIM Offboarding.
A removed membership appears under Inactive. The removal affects access to this organization and its workspaces, including access through the member's personal API tokens for this organization. The person's Shiplight account, login methods, history, and memberships in other organizations are preserved. Organization-owned resources and organization API tokens remain with the organization.
Restoring access
An owner can find the member under Inactive, select Reactivate, and confirm. Reactivation preserves the member's previous role and is subject to the organization's member limit. An owner can also issue a new invitation; accepting it restores membership with the invited role.
For employees using a company identity provider (IdP), restore their intended application access there as well. Re-enabling a directory user or signing in with SSO does not automatically restore an inactive Shiplight membership.
Organization settings
Settings → Organization 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.
When enabled, Enterprise SSO and SCIM Offboarding also appear on this page. Member management, subscriptions, billing, invoices, and integrations have their own pages under Settings. See Billing & Usage for subscription and payment details.
Integrations
Owners can connect GitHub and choose which repositories to share at Settings → Integrations. The connection is required for CI Runners and adds repository and change details to your test results.
See CI Runners → Setup for installation steps and required permissions.
Enterprise SSO
Enterprise SSO lets employees sign in with their company identity and lets eligible employees join the organization as members on their first successful sign-in.
SSO is not enabled automatically with an Enterprise plan. Contact your Shiplight administrator to enable it for your organization. Once enabled, an organization owner can complete setup at Settings → Organization.
The Provider shown there is WorkOS or Scalekit, configured by Shiplight. Setup opens that provider's portal. Existing members keep their roles and existing sign-in methods when using SSO.
See Enterprise SSO for setup instructions, employee sign-in, and troubleshooting.
SCIM Offboarding
SCIM Offboarding automatically removes matching ordinary members when the company directory reports a user deletion or deactivation. It also cancels matching pending invitations. Directory changes can take time to appear in Shiplight.
SCIM is not enabled automatically with an Enterprise plan or an SSO connection. Contact your Shiplight administrator to enable it separately. Once enabled, an organization owner can connect the directory at Settings → Organization, using the same WorkOS or Scalekit provider as SSO.
SCIM does not create or restore memberships, change roles, or remove owners. Handle owner departures manually, and use Restoring access when a former member needs to return.
See SCIM Offboarding for directory setup, removal behavior, and restoring access.
Switching organizations
If you belong to multiple organizations, open the organization menu in the app sidebar and choose another organization under Switch organization. The menu shows your role in each organization.
Switching changes the organization whose data and settings you are viewing. Your permissions depend on your role in the selected organization. API tokens remain scoped to the organization they were created for; switching the browser's active organization does not change a token's scope.
Related
- Billing — plans, usage, and invoices
- API Tokens — personal versus organization tokens
- CI Runners — connecting GitHub and enabling runners