Preserve Extension Storage to Keep Users Signed In

The ScreenSteps Sidekick extension does not use browser cookies to keep the extension signed in. After sign-in, the extension stores authentication tokens in Chrome/Edge extension storage, which is part of the user’s browser profile.

Clearing only cookies and cache should not sign users out of the extension. However, anything that removes extension storage, resets the browser profile, removes the extension, or reinstalls the extension can require users to sign in again.

If you reset browsers nightly, make sure the ScreenSteps Sidekick extension data is preserved.

Do not delete the browser profile or the extension’s local storage folder for the deployed extension ID.

Common production paths:

• Windows Chrome: %LOCALAPPDATA%\Google\Chrome\User Data\<Profile>\Local Extension Settings\kjnpdblaciideghjecicchjnjpmodnfp
• Windows Edge: %LOCALAPPDATA%\Microsoft\Edge\User Data\<Profile>\Local Extension Settings\mmhfdlbngmgnfphepihackgejcjepmkj
• macOS Chrome: ~/Library/Application Support/Google/Chrome/<Profile>/Local Extension Settings/kjnpdblaciideghjecicchjnjpmodnfp
• macOS Edge: ~/Library/Application Support/Microsoft Edge/<Profile>/Local Extension Settings/mmhfdlbngmgnfphepihackgejcjepmkj

The extension ID may be different if your organization deploys a beta build, self-hosted package, or a Chrome Web Store extension into Edge. Confirm the extension ID in chrome://extensions or edge://extensions.

If using a “clear browsing data on exit” policy, clearing only cookies and cached files should be fine. Avoid policies, scripts, profile reset tools, VDI cleanup rules, or security tools that remove extension data, browser profile data, or the extension itself.

For non-persistent VDI, roaming profiles, or mandatory profiles, persist the extension’s Local Extension Settings folder across sessions, or exclude it from profile reset.

If you only clear cookies and cache, users should stay signed in to the extension.

Required Permissions

Do not block the permissions requested by the extension.

The extension requires:

• storage
  Required to save authentication state and user settings.
• tabs
  Required for browser tab integration.
• activeTab
  Required for interacting with the current page.
• scripting
  Required in Chrome and Edge for page integration.
• offscreen
  Required in Chrome and Edge for background extension workflows.
• Host access to ScreenSteps sites
  Required so the extension can communicate with ScreenSteps and customer ScreenSteps domains.

Do not configure blocked_permissions in a way that blocks any of the permissions above.

Required URL Access

The extension must be allowed to access:

• Your ScreenSteps site
  • Example: https://yourcompany.screenstepslive.com
  • Example: https://help.yourcompany.com
• The ScreenSteps extension API domain
  • Example: https://extension.screenstepslive.com
• The extension setup page
  • Example: https://yourcompany.screenstepslive.com/extension/setup
• The OAuth callback page
  • Example: https://yourcompany.screenstepslive.com/extension/oauth-callback

If your organization uses custom domains, allow those domains as well.

Policies That Must Not Block the Extension

Review Chrome and Edge ExtensionSettings policies.

Make sure the extension is not affected by:

• installation_mode: "blocked"
• installation_mode: "removed"
• blocked_permissions
• runtime_blocked_hosts
• minimum_version_required set higher than the installed extension version
• Incorrect or missing update_url
• Security software or browser management tools that remove unapproved extensions

If runtime_blocked_hosts is used globally, add ScreenSteps domains to runtime_allowed_hosts.

Actions That May Require Users to Sign In Again

Users may be asked to sign in again if IT performs any of the following actions:

• Uninstalls or reinstalls the extension
• Clears the browser profile
• Deletes the user’s Chrome or Edge profile data
• Uses a cleanup/security tool that removes extension data
• Blocks required ScreenSteps domains
• Blocks required extension permissions
• Disables the extension because of a minimum version policy

Extension updates should not normally require users to sign in again, as long as the extension is updated in place and not removed.

Force-Pin the Extension to the Toolbar

By default, force-installed extensions are installed unpinned — the icon is hidden in the browser's extensions (puzzle-piece) menu. To keep the ScreenSteps Sidekick icon visible at all times, set the toolbar pin policy.

Chrome (ExtensionSettings):

{
  "kjnpdblaciideghjecicchjnjpmodnfp": {
    "toolbar_pin": "default_pinned"
  }
}

Microsoft Edge (ExtensionSettings):

{
  "mmhfdlbngmgnfphepihackgejcjepmkj": {
    "toolbar_state": "default_pinned"
  }
}

Troubleshooting Checklist

On an affected device, check the following.

Chrome

Open:

chrome://policy
chrome://extensions

Confirm:

• The extension appears in chrome://extensions.
• The extension ID matches the expected ID.
• The extension is enabled.
• The extension is installed by policy.
• The extension version meets any minimum_version_required policy.
• No policy is blocking required permissions.
• No policy is blocking ScreenSteps domains.

Microsoft Edge

Open:

edge://policy
edge://extensions

Confirm:

• The extension appears in edge://extensions.
• The extension ID matches the expected ID.
• The extension is enabled.
• The extension is installed by policy.
• The extension version meets any minimum_version_required policy.
• No policy is blocking required permissions.
• No policy is blocking ScreenSteps domains.