Managed configuration

The SlashID Browser Extension reads its settings from the browser's managed storage (chrome.storage.managed). Whatever you deliver through enterprise policy is validated against the schema shipped with the extension before the extension sees it: keys that are not in the schema are dropped, and a value of the wrong type is rejected.

Keys

Key	Type	Required	Description
sidEventStreamingToken	string	Yes	The activation code of your SlashID Sensors data source.
sidSilentOnboarding	boolean	No	When true and the token is also managed, the extension registers and signs the user in without any prompts. Defaults to false.

A token that is empty or only whitespace is ignored, and the extension falls back to asking the user for one. sidSilentOnboarding has no effect unless a managed token is present - see Silent Onboarding for the other requirements of that flow.

Schema

This is the JSON Schema the extension ships as managed_storage_schema.json. You can validate your policy against it before deploying.

{
  "type": "object",
  "properties": {
    "sidEventStreamingToken": {
      "title": "SlashID Event Streaming Token",
      "description": "Event Streaming Token used for pushing events",
      "type": "string"
    },
    "sidSilentOnboarding": {
      "title": "SlashID Silent Onboarding",
      "description": "When true and the event streaming token is also managed, the extension onboards and logs in without user interaction",
      "type": "boolean"
    }
  }
}

Verifying on a device

Open chrome://policy (or edge://policy) on a managed device and find the extension by its ID. The page shows every managed value as the browser parsed it, along with its type. A value that failed schema validation appears there with an error instead of failing silently in the extension.