WORKSPACE · Airline employee portal and access management One work account. Every application you have been granted.

WORKSPACE is an airline employee portal with access management: staff sign in with their Microsoft work account to find every workspace application they have been granted on one page, with their access level and any restriction, and administrators set up new colleagues' access before first sign-in. WORKSPACE applies each application's role rules, and every launch re-reads current roles from its own identity service, connected to Microsoft Entra, so a removed grant is refused.

Bring your own scenario. We agree what to measure before you decide. How an evaluation works ↓

Email me the brochure, WORKSPACE
Employees and the IT and identity administrators who manage their accessDeployed per operatorFits your operation as it changes
WORKSPACE application cards for a synthetic employee: EPHOR Ai at Approved training only, CREW Ai at Editor · Crew only, FLIGHT Ai at Viewer and PINAX Ai at Viewer, each with a Web version badge and an Open app link, using synthetic demonstration data.
Each card at one level, with any restrictionDemonstration data · Click to enlarge
In brief

What is WORKSPACE?

WORKSPACE is FlightAtom's employee portal and access management service for airlines. Employees sign in with their Microsoft work account and see every workspace application they have been granted, with their access level and any restriction. Administrators assign access per application, have new employees' accounts ready before their first sign-in, and can preview what a colleague sees.

Category
Airline employee portal and access management
Built for
Employees and the IT and identity administrators who manage their access
Automation
Deterministic role rules decide every card, launch, and preview
Availability
Deployed per operator · independent product
Fits your operation
As your operation grows or changes, we adapt WORKSPACE to fit, and you approve each change before it goes live.
How it works · WORKSPACE

Restrictions outrank broader grants. No role, no card.

Each application's own role rules turn a person's assigned roles into one card at one access level, or no card, and run again at every launch and in an administrator's preview.

DELPHI AiCREW AiPINAX AiEPHOR Ai
DispatcherEach grant shows at its assigned level, and with no EPHOR Ai role, EPHOR Ai never appears.ViewerViewerEditorNo card
Training captainGranted Admin in CREW Ai and EPHOR Ai, but a restriction in each outranks that grant.EditorEditor · Crew onlyViewerApproved training only
Cadet pilotA learning-only restriction in DELPHI Ai outranks the broader role it is paired with.Learning OnlyNo cardViewerNo card
Duty managerHolds two DELPHI Ai roles that DELPHI Ai treats as conflicting, so the card is hidden and a launch refused.No cardViewerAdminNo card
New starterCreated by the daily directory import with no password and no access, so groups can be assigned before first sign-in.No cardNo cardNo cardNo card
Example with fictional employees and role assignments, showing the card each would see for each application.
Inside WORKSPACE

From sign-in to the right application.

Current product interface with a synthetic account, synthetic colleagues and neutral presentation branding. Open a screenshot to inspect the workspace.

01 / WORKSPACE

Signed in with one work account

Employees sign in with their company Microsoft account, and the Account panel shows who is signed in, notes that the organisation manages the account and its application access, and offers Sign out. Synthetic demonstration data.

WORKSPACE "Your account" panel open over the Applications page under a neutral Demo Airline label, showing a Microsoft logo beside the synthetic employee Alex Demo and alex.demo@example.test, the line "Your Microsoft account and application access are managed by Demo Airline", a Sign out button and a Close button, with the dimmed application cards and the sidebar visible behind, with synthetic demonstration data.
Signed in with one work accountDemonstration data · Click to enlarge
02 / WORKSPACE

Granted workspace applications and their levels

Each employee sees only the applications their roles grant, with the access level and any restriction each application's rules apply, and can arrange the cards in their own order. Synthetic demonstration data.

WORKSPACE Applications page under a neutral Demo Airline label, showing application cards for a synthetic employee in a saved order: EPHOR Ai at Approved training only, CREW Ai at Editor · Crew only, TRACE Ai (Beta) at Editor, FLIGHT Ai at Viewer, PINAX Ai at Viewer and DELPHI Ai at Viewer, each with a Web version badge and an Open app link, with HIRE Ai, MENTHOR Ai and VISION Ai below, plus All apps and Favorites tabs, a Find an application search, Reset order, Grid and List views and a Refresh access button, with synthetic demonstration data.
Granted workspace applications and their levelsDemonstration data · Click to enlarge
03 / WORKSPACE

Add links for chosen groups

Portal administrators add links to other applications and choose who sees each one, from all employees to a directory group, and the links appear beside the applications people are granted and in Support/Requests. Synthetic demonstration data.

WORKSPACE Manage apps page with an Add application button and a table of three added applications with example.com links: Crew Rest Calculator visible to all employees, Pilot Library visible to the /Flight Operations/Pilots group and Cabin Service Guide visible to the /Cabin Crew group, each with its update date and Edit and Remove buttons, with synthetic demonstration data.
Add links for chosen groupsDemonstration data · Click to enlarge
04 / WORKSPACE

Directory for portal administrators

Portal administrators search the directory by name or email and see each person's department and whether their account is enabled. Synthetic demonstration data.

WORKSPACE People page with a Search name or email field and a directory table of six synthetic accounts with example.test addresses and their departments (a dash for the service.desk account, which has none), Enabled or Disabled status (Morgan Demo is Disabled) and a View workspace button on each row, followed by "Showing 1–6" and Previous and Next buttons, with synthetic demonstration data.
Directory for portal administratorsDemonstration data · Click to enlarge
05 / WORKSPACE

Preview a colleague's workspace

For portal administrators, View workspace opens a read-only, logged preview built with the same rules as the colleague's own workspace, so Learning Only on DELPHI Ai and Crew only on CREW Ai appear as they would for them. Synthetic demonstration data.

Read-only preview of synthetic colleague Avery Sample's workspace, with a banner saying app launches, favorites and ordering are disabled and an Exit preview button, the subtitle "Applications assigned · Flight Operations", and cards for DELPHI Ai at Learning Only, MENTHOR Ai at Editor, PINAX Ai at Viewer and CREW Ai at Viewer · Crew only, plus two added links, Crew Rest Calculator and Pilot Library, marked Shared link, with synthetic demonstration data.
Preview a colleague's workspaceDemonstration data · Click to enlarge
06 / WORKSPACE

Support tickets and requests

Employees follow the support tickets and requests they have sent, each with its application, status and last update. Synthetic demonstration data.

WORKSPACE Support/Requests page listing five synthetic requests in a table with Subject and type, Application, Status and Updated columns: a CREW Ai support ticket In progress, a VISION Ai request Open, a FOLIO Ai support ticket Awaiting your reply, a MENTHOR Ai support ticket Resolved and a Workspace / general support ticket Closed, with a New request button, with synthetic demonstration data.
Support tickets and requestsDemonstration data · Click to enlarge
07 / WORKSPACE

One conversation per request

Each request shows its application, priority, status and description, with the replies in one conversation and a box to answer. Synthetic demonstration data.

WORKSPACE support ticket detail for a synthetic CREW Ai support ticket titled New roster period not showing in crew self-service, marked In progress, with Application CREW Ai, Priority High and an updated time, a one-line description, and a Conversation with two messages from You and a reply from Client Services, with synthetic demonstration data.
One conversation per requestDemonstration data · Click to enlarge
Capabilities

From the directory import to the application they open.

Access follows each person's Microsoft directory account and the roles an administrator assigns, and employees get one place to open, arrange, and ask for help with their applications.

Granted applications on one page

Each employee sees only the applications their roles grant, each with a short description, the access level they hold, and any restriction that applies. My access lists what they can open and at which level, and Refresh access shows an administrator's change straight away. Portal administrators can also add links to other applications, for everyone or for chosen directory groups, and those links appear beside the granted applications.

One Microsoft sign-in for every connected application

Employees sign in with their Microsoft work account, where the organisation's multi-factor authentication and conditional access policies apply, and open connected applications from the workspace without signing in again. WORKSPACE ships with its own identity service, built on Keycloak and connected to the organisation's Microsoft Entra tenant, with a separate sign-in client and roles for each application. Its sign-in, account, and administration pages carry the operator's branding.

Restrictions hold, even over Admin

WORKSPACE applies each application's own role rules, so a learning-only, crew-only, or approved-training-only restriction holds even when the person is also granted Admin. Role combinations an application treats as conflicting hide the card and block the launch.

Accounts ready before the first sign-in

Administrators can assign a new colleague's applications before their first sign-in, because a daily import from Microsoft Entra creates an account for each enabled internal member, linked by the directory's immutable object ID with no password and no access. The same import keeps each person's department in step.

Every launch uses current access

Every launch from the workspace re-reads the person's current roles from the identity service, so a removed grant is refused and a disabled account is signed out of the workspace. Each launch opens only an approved HTTPS destination, and where an application has separate administration and user entry points, the current role decides which one opens.

Preview what a colleague sees

Portal administrators search the directory by name or email, see each person's department and whether their account is enabled, and open a read-only preview that applies the same rules as the real workspace, restriction labels included. Every preview is logged. Administrators in a dedicated identity group can also impersonate the person from the identity console; unlike the preview, this is a real sign-in as them, and the identity service records it as an audit event.

Short-lived tokens and a clean sign-out

Tokens and secrets stay on the server, access tokens last two minutes, and each portal session closes after eight hours. Signing out revokes the refresh token, ends the identity session, and marks the portal session revoked, so a request already in flight cannot bring it back.

Support requests from the workspace

Employees send FlightAtom a support ticket or a request about a specific application or the workspace in general, set a priority from low to urgent, and follow its status and replies in one conversation.

Find, favourite, and arrange

Find an application with the / shortcut, keep favourites, switch between grid and list, and reorder cards from the keyboard with screen-reader announcements. Applications granted after the person's first visit in that browser carry a New badge for two weeks, and appearance follows the device setting until they pick Light or Dark.

Workflow & control

One identity. One set of rules. Checked at every launch.

WORKSPACE is deterministic. The identity service holds every grant, and the same per-application role rules decide each card, each launch, and each administrator preview, with access denied unless a role grants it.

One set of rules for every view

Card visibility, the access level shown, the launch check, and the administrator's read-only preview all run the same role rules, so a preview shows what that person's current roles produce.

Matched by directory ID, never by email

Microsoft sign-ins are matched to accounts by the directory's immutable object ID from a validated single-tenant token, never by email address. A custom sign-in provider, tested in every identity-service build, migrates existing accounts in place with their groups and roles intact.

Identity setup checked for drift

Each deployment's identity setup is scripted, and a read-only verifier fails if sign-in stops being Microsoft-only, PKCE or HTTPS is missing, a default group or role would grant application access, or sign-in and administrator audit events are switched off.

Evaluate WORKSPACE

Make the next step measurable.

Agree a representative sample and a baseline from your current process. These are proposed evaluation measures, not published performance results.

Bring a representative example

Test accounts with different application grants, including one with no access.

Inspect the complete workflow

Sign in, compare each person's cards and levels with the assigned groups, change a grant, refresh, and attempt a launch that should be denied.

Compare with your baseline

Agreement between assigned access and visible cards; time for a change to appear; denied launches for removed access.

Questions & answers

Before you book a demo.

Does WORKSPACE provide single sign-on?

Yes, for the applications connected to its identity service. WORKSPACE includes its own Keycloak identity service, and each connected application signs people in through it with its own client and roles, so employees use one Microsoft work account for the workspace and those applications. A launch from the workspace re-checks the person's roles, then hands them to that application's own sign-in.

Which identity provider does WORKSPACE use?

Microsoft Entra ID. WORKSPACE's Keycloak identity service connects to one organisation's Entra tenant and has no password form of its own, so people authenticate at Microsoft, where the organisation's multi-factor authentication and conditional access policies apply. Accounts are matched by the directory's immutable object ID, never by email address.

How do new employees get access before their first sign-in?

A daily import from Microsoft Entra creates an account for each enabled internal member, linked by directory object ID with no password and no access, and keeps each person's department up to date. Administrators can assign application groups before the person first signs in, and optional baseline policies can give every imported employee viewer access to DELPHI Ai or PINAX Ai.

How is access granted or removed?

An administrator adds or removes a person's application groups in the identity service's administration console, which portal administrators open from the Manage access shortcut. Every launch re-reads the person's current roles, and Refresh access shows a change straight away. When someone leaves, an administrator disables the account and signs out its sessions, because the daily import adds and updates people but does not remove them.

Can an administrator see what a colleague sees?

Yes. Portal administrators can search the directory by name or email, see each person's department and account status, and open a read-only preview that applies the same rules as the real workspace, including access levels and restriction labels. Nothing is opened or saved for that person, and every preview is logged.

Does WORKSPACE replace each application's own permissions?

No. WORKSPACE decides what a person sees and can launch, and each application still validates the sign-in and enforces its own permissions. A connected application can also be given its own service connection to the identity service, so its backend can re-check whether a person is still enabled and which of that application's roles they currently hold.

How does WORKSPACE decide what each person sees?

With role rules. WORKSPACE is deterministic: each application's role rules decide every card, launch, and administrator preview, and access is denied unless a role grants it.

Does WORKSPACE require AURORA Ai or another FlightAtom product?

No. WORKSPACE is a separate product that lists the applications configured for a deployment. Each listed application remains an independent product with its own sign-in integration.

What happens to WORKSPACE when our operation grows or changes?

As your fleet, routes, rules or teams change, we adapt WORKSPACE to match, and you approve each change before it goes live.

See WORKSPACE in action

Bring your application list and access model.

A focused walkthrough, with the people and decisions that matter to your team.

Request a demo