Enterprise

Enterprise deployment

In an organisation, the server address can be pushed to every browser through Chrome’s managed storage instead of being typed by each user. Users then get a working extension right after installation and cannot point it elsewhere.

Managed configuration

The extension reads a single policy key:

endpoint (string): base URL of the Screenshotter server, e.g. https://screenshots.corp.example.com. The extension appends the /upload path itself, so it must not be part of the value.

When a managed endpoint is set:

it is applied as soon as the extension is installed;
the options page shows it read-only, with a notice that it is managed by the organisation, and its Save and Reset buttons are disabled;
the other options (screenshot effect, quick upload) stay user-configurable.

Without a policy the extension behaves normally.

Nothing changes on the server side: the same CORS and authentication settings apply whether the endpoint was configured by a policy or by the user.

Deploying the policy

The policy is a JSON document applied to the extension by its ID (nnipkgjcfgekggpkclhdghbbfnpokdlg for the Web Store build):

{
  "endpoint": "https://screenshots.your-corp.com"
}

Google Workspace Admin Console

Go to Devices → Chrome → Apps & extensions.
Find Screenshotter, or add it by ID from the Chrome Web Store.
Under Policy for extensions, upload the JSON file above.
Assign it to the relevant organisational units.

Windows (registry)

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\<extension-id>\policy]
"endpoint"="https://screenshots.your-corp.com"

macOS (managed preferences)

Create a plist at /Library/Managed Preferences/<bundle-id>.plist:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>endpoint</key>
  <string>https://screenshots.your-corp.com</string>
</dict>
</plist>

Extension