Account structure, permissions, and sharing in FlightWiseOS

A control layer around accounts

Companies and family offices don’t fly as one person. They fly as offices, cost centers, executives, and client families — each with its own budget, its own team, and its own need for privacy.

FlightWiseOS gives them an account structure that matches how they’re organized. Parent accounts and sub-accounts, user permissions, visibility rules, and shared programs let everyone work independently and as a team, while the organization keeps control at the top.

Parent accounts and sub-accounts

FlightWiseOS accounts work in a parent and child structure.

• A parent account represents the organization: the company, the enterprise, or the family office.
• Sub-accounts sit beneath it: an office, a cost center, an executive, or a client family.
• Records track up and down the structure. Each sub-account keeps its own flights, providers, and spend. The parent account sees roll-up records across every sub-account.

Organization	Parent account	Sub-accounts
Corporation	The company	Offices, cost centers, executives
Family office	The family office	Each client family
Holding company	The holding company	Portfolio companies
Executive team	The team	Each executive’s personal flights

Users, roles, and permissions

Each account has users, and each user has permissions.

• Admins set up the account, its people, and its rules.
• Users book and manage flights within what they’re allowed to do.
• Account permissions decide which accounts a person can see and act in.

That means an executive can book from their own account, their assistant can work in the same account, and finance can see billing and ledgers — each with the access that fits their job. See How teams use FlightWiseOS for examples.

Visibility rules

Visibility decides who sees what.

• A sub-account can be private to its own team. A family office can give each client a sub-account no other client can see.
• The parent account can see across sub-accounts, so leadership has the whole picture.
• Billing contacts receive billing information without seeing more than they need.
• Each person sets their own notification preferences — push, email, or both.

Controls set at the parent level

From the parent account, an organization can set controls that apply to its sub-accounts:

• Approved providers — which operators and programs can be used.
• Safety standards — the requirements every flight must meet.
• Booking limits — how much a person or account can book.

Sub-accounts still run on their own day to day. The parent sets the guardrails.

Enterprise sharing of programs, providers, and services

Organizations often buy aviation products centrally and use them across teams. FlightWiseOS supports that with enterprise sharing.

• Put a program into FlightWiseOS — for example, a fractional share with 100 hours — and split it among several executives or offices.
• Share preferred providers and services across sub-accounts, so every team books from the same approved list.
• Track who used what, so each office’s share of the program is clear.

Roll-up reporting

Because every flight runs through FlightWiseOS, the parent account can see:

• Spend across all sub-accounts, and by each one
• Program usage and remaining balances, including shared programs
• Spend by provider, destination, aircraft, and season
• Who is flying, how often, and with whom

Each sub-account sees its own numbers. The parent sees them all. See Track Spend.

Who this is built for

• Corporate executive teams that need cost centers and offices to operate independently under one structure.
• Family offices that run travel for several families and must keep each one private.
• Holding companies and enterprises that buy programs centrally and share them across teams.
• Any organization that needs to decide exactly who sees what.

Plans

Multi-account structures, permissions, cross-account visibility, program sharing, and custom reporting are part of the Enterprise plan, configured to each organization. See pricing or request a demo to talk through your structure.