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.