Click the app. FirmBrowser does the rest.
Identity proves who you are. FirmBrowser governs what happens next — from the moment the managed browser launches to the audit record left behind.
- Step 01
User launches FirmBrowser
The managed browser environment starts under enterprise policy.
- Step 02
User and device context verified
Identity, role, device posture and access period are checked before anything opens.
- Step 03
Recipe Book made available securely
The user's authorised applications and policies are released to the session under policy.
- Step 04
User clicks the application
One click. No usernames, no passwords, no MFA fumbling.
- Step 05
Correct authentication method chosen
SSO hand-off to an approved identity provider, or execution of the authorised login recipe.
- Step 06
Application opens
The user lands inside the app in a controlled browser context.
- Step 07
Post-login controls keep applying
URL Rules, Element Rules, workflow restrictions and data-movement policy stay in force.
- Step 08
Security and audit events recorded
Access, blocked actions and policy events become defensible evidence.
- FirmBrowser does not stop working when the login page disappears. Authentication is an event — FirmBrowser governs the session.
One experience, two authentication models
FirmBrowser hands off to your identity provider where the application supports it, and executes an authorised App Recipe where it does not.
One click for the user
The user clicks the app. FirmBrowser determines the correct authentication method and takes care of the rest.
Native SSO
Where an application supports your organisation's preferred identity provider, FirmBrowser launches the application and lets authentication be handled by that approved platform — Entra ID, Okta, Google Identity or another approved SAML/OIDC provider.
- Identity stays with your identity platform
- FirmBrowser continues browser and session controls
- Post-login policy still applies
Recipe-driven access
Where an application does not use your preferred SSO mechanism, FirmBrowser can use a secure App Recipe to perform the authorised login workflow on the user's behalf.
- The user never knows or types the password
- Nothing to copy, save, share or remember
- Same controls apply after login
Different authentication technologies underneath. One controlled experience for the user.
Security does not stop when the login page disappears
The same cloud application, presented as the role is permitted to use it.
- Dashboard
- Reports
- Settings
- Users
- Admin
- Export
- Download
- Delete
- Change Password
- Billing
Every user sees every function the application ships with.
- Element Rules
- URL Rules
- Role Policy
- Dashboard
- Reports
- Approved Workflow
- Element Rule — Settings, Admin, Users removed
- URL Rule — password-reset route redirected
- Export — blocked
- Password Reset — restricted
Same cloud application. Different permitted experience.
One control plane for browser-based applications
Manage users, devices, identity providers, applications, Recipe Books, rules, credential policy, audit and compliance evidence from a single place.
Authentication is an event. FirmBrowser governs the session.
See the full access flow applied to your firm's own cloud application stack.