Team and Organization Accounts
How AeroCopilot multi-tenant organizations work — creating an org, inviting members by email, managing roles and permissions, and the owner-only delete control.
Team and Organization Accounts
AeroCopilot supports multi-tenant organizations on top of personal accounts. An organization is a shared workspace — a flight school, a charter operator, a training department, or a flying club — with its own name, logo, members, and role hierarchy. This page explains how organizations work in AeroCopilot today and which controls you have.
Personal account vs. organization
Every AeroCopilot user starts with a personal account. An organization is created on top of that and becomes an additional context you can switch into. Most settings (profile, certificates, alert preferences, theme) stay on your personal account. Organization-scoped settings live under /settings/organization and /settings/members and only apply when you are operating in that organization context.
Organization settings
The organization settings page (/settings/organization) lets members with the right permissions edit:
- Organization image / logo — uploaded via the image form and used wherever the organization is shown in the UI.
- Organization name — display name shown in the breadcrumbs and member-facing surfaces.
Both controls are gated by an organization:update permission check. If your role does not grant that permission the fields render disabled.
Members and invitations
The members page (/settings/members) shows two tables:
- Members — current members of the organization, with role badges.
- Invitations — pending email invitations and their status.
If your role grants invitation:create you will see the invite control. Inviting a member sends an email invitation with instructions to join the organization. The invitee follows the link, signs in (or signs up), accepts, and lands inside the organization with the role you assigned.
Pending invitations can be resent if you have invitation:create, and cancelled if you have invitation:cancel. These two permissions are independent so an organization can let admins resend without granting cancellation rights.
Roles and permissions
Out of the box AeroCopilot ships three roles:
- Owner — full access to all organization resources and settings.
- Admin — can manage members, billing, and most organization settings.
- Member — basic access with the ability to invite others.
The roles page (/settings/roles) lets organizations create custom roles in addition to these defaults. Custom roles define:
- A lowercase role name (letters, numbers, hyphens, underscores) that is locked once created.
- A hierarchy position relative to an existing role (above or below). Hierarchy levels determine who can manage whom.
- A description and a permission set assembled from the available organization permissions.
A role that is currently in use (members assigned, or pending invitations targeting it) cannot be deleted. The UI surfaces this with a "This role is currently in use" warning so you know to reassign first.
The creator and the delete control
The organization creator has a privilege no other role gets: the ability to delete the organization. The settings page renders a Delete organization card only when the current user is the creator (determined by walking the role hierarchy and matching the creator role). For everyone else — including admins — the card is hidden.
Deleting an organization removes the workspace and its membership records. Personal accounts of the members continue to exist; only the shared workspace and its scoped data are removed.
Switching between contexts
If you belong to more than one organization you can switch the active context from the app shell. AeroCopilot stores the active organization on your session, so subsequent server requests resolve permissions against the right workspace.
What is and is not included today
AeroCopilot organizations cover identity, membership, role-based access, invitations, and per-org settings. That is the foundation provided by Better Auth's organization plugin. Single Sign-On (SSO/SAML) and SCIM-based directory provisioning are not part of the current organization product. If your operation needs them, contact us before you onboard so we can confirm fit and timeline.
Related
- Profile and Pilot Type Settings —
/help/account/profile-settings - Email and Push Notifications —
/help/account/notifications - Installing AeroCopilot as a Mobile App (PWA) —
/help/account/mobile-pwa