Silent Onboarding
By default, a freshly installed extension asks the user to finish setup themselves: activate it, wait for registration, and sign in through your identity provider. On managed browsers you can skip all of that. With silent onboarding, the extension registers itself and signs the user in as soon as it is installed, without showing a single prompt.
Silent onboarding works on Chromium-based browsers (Chrome, Edge) deployed through enterprise policy, and requires extension version 1.18.0 or later.
Requirements
Browser policy
Deploy the extension through your browser's enterprise policy, following the Enterprise Deployment Guide, and set two managed storage values:
| Key | Type | Value |
|---|---|---|
sidEventStreamingToken | string | The Event Streaming Token from the SlashID Console |
sidSilentOnboarding | boolean | true |
Both are required. If you set sidSilentOnboarding without a managed token, the extension ignores the flag and runs the standard onboarding flow.
SlashID configuration
On the Browser Extension configuration page in the SlashID Console:
- Enable Silent login. Without it, the extension still registers silently, but the sign-in step falls back to the interactive flow.
- Configure an OAuth-based identity provider for the extension. Silent sign-in runs your IdP's OAuth flow in the background, so a connection with only SAML credentials cannot sign users in silently.
- If Require IDP authentication is enabled, silent onboarding covers the sign-in step too. If it is disabled, setup completes after registration and no sign-in happens at all.
If your IdP is Microsoft Entra ID, grant tenant-wide admin consent to the app registration whose client ID is configured on the connection. Silent sign-in runs with prompt=none, which cannot show a consent screen - a user without consent on record falls back to the interactive flow, and in tenants where user consent is disabled they stay stuck there until an admin consents. The extension only asks for the basic sign-in scopes (openid, profile, email, User.Read).
Browser profile
Silent sign-in uses the email of the account signed in to the browser profile as the login hint, so users must be signed in to the browser with the account your organization manages. They also need an active session with your identity provider in that profile - the flow runs without user interaction, so it cannot ask them to enter credentials.
What users see
Almost nothing. The extension registers on install and again on every browser start, without banners or badge notifications. If someone opens the extension popup or options page while setup is still running, they see an Automatic setup screen explaining that their organization is setting the extension up for them. This usually takes under a minute, after which the extension is active and the user is signed in.
When it can't complete
Silent onboarding never blocks anyone. If a step fails, the extension falls back to the regular onboarding flow from wherever it got to - for example, if registration succeeded but silent sign-in did not, the user sees the usual Authentication required banner and signs in once by clicking Log in.
If your users keep landing on that banner, work through the requirements above. The most common causes are a missing IdP session in the browser profile, a profile signed in with a personal account, Silent login being disabled in the Console, and (on Entra ID) missing admin consent for the app registration.