Skip to content

Screshot for teams

Share sensitive screenshots with your team. Only your team.

Capture, blur and point at the problem, then share it with everyone in your workspace in one click. Each screenshot is encrypted on the sharer's computer: your team holds the keys, Screshot never does.

Workspaces

Start a team in two minutes

No sales call, no seats to buy. Anyone can create a workspace and invite their team.

  1. Install

    01

    Everyone adds Screshot to Chrome. Capture, blur and annotate work right away, with no account.

  2. Sign in and turn on encryption

    02

    Sign in with Google and set up a passkey and a recovery code, once per person.

  3. Create a workspace

    03

    Name it after your team and invite colleagues who have a Screshot account.

  4. Share with Workspace

    04

    Click Share, choose Workspace and pick the team. Everyone in it can open the screenshot.

  • One click for the whole team

    The sharer's browser gives each member their own copy of the screenshot's key, so Screshot never holds it.

  • Owners and admins manage people

    Invite colleagues, make admins, remove members. Invitations are accepted by the invitee.

  • Access ends when membership does

    Remove someone and they lose the team's screenshots and their copies of the keys. Their own shared screenshots go back to Only me.

  • Talk about it, privately

    Comments, replies and @mentions on every shared screenshot, end-to-end encrypted too. Mention a teammate and they get an email, without the comment's text.

For your security team

Easy to say yes to

When someone asks whether it's safe to put customer screenshots in Screshot, these are the answers.

Private by default

Screenshots are created, blurred and edited inside the browser. Nothing reaches Screshot unless someone chooses to share it.

5 narrow permissions

activeTab, scripting, contextMenus, storage and identity. No host permissions, no access to browsing history, no install warnings.

Nothing to provision

Capture and blur need no accounts or licenses. People sign in with Google only when they want to share.

Updates from the Chrome Web Store

A standard extension: install, pin or remove it with the Chrome policies you already use.

How Screshot answers a security review

The questions a security team asks first, Screshot's answer to each, and where to check it yourself.

Where do captures go?
Nowhere, unless someone shares one. Capture, blur, copy and download happen in the browser.
How to check it: Inspect the extension's service worker and watch the Network tab while capturing: no requests.
What is stored on Screshot's servers?
Only screenshots someone chooses to share, as encrypted files, plus account and sharing details such as titles, sizes and invited emails.
How to check it: The data inventory in the security review pack.
Who holds the keys?
The sharer and the people they choose. Screshot never receives a readable key, unless someone reporting abuse chooses to send it with the report.
How to check it: Inspect a share upload: encrypted bytes that start with SCE1, and no request carries the key.
Who can open a new share link?
Only its owner. Every new link starts as Only me until the owner changes it.
How to check it: Share a screenshot and open the link in another browser profile.
Which browser permissions does it need?
5: activeTab, scripting, contextMenus, storage and identity. No host permissions, and none shows an install warning.
How to check it: Open chrome://extensions and click Details on Screshot.
Is there analytics or telemetry in the extension?
None. No analytics, no crash reporting and no remote code.
How to check it: Watch the service worker's Network tab, or read the extension's files.
Where is data stored?
Servers and database at AWS in Frankfurt. Encrypted files in Cloudflare R2, in the EU jurisdiction.
How to check it: The subprocessors in the security review pack and the privacy policy.
Which certifications does Screshot hold?
None yet: no SOC 2 or ISO 27001, and no independent penetration test so far.
How to check it: The questionnaire answers in the security review pack.

How the encryption works, what Screshot can and can't see, and its limits: security overview and the security review pack for questionnaires.

For IT

Install it for everyone

Optional. Screshot is a standard Chrome Web Store extension, so any Chrome management tool can install and pin it. Each person still signs in with Google and turns on encryption the first time they share.

Google Admin consoleChrome Browser Cloud Management or ChromeOS
  1. Go to Devices → Chrome → Apps & extensions → Users & browsers.
  2. Select the organizational unit to deploy to.
  3. Click + → Add Chrome app or extension by ID, and paste the ID below (From: Chrome Web Store).
  4. Set Installation policy to Force install + pin to browser toolbar, then Save.
Extension ID
ikhdemckhflgmlijkaomcpdmljegkakh
Microsoft IntuneWindows devices with Google Chrome
  1. Go to Devices → Configuration → Create → New policy (Windows 10 and later, Settings catalog).
  2. Add the setting Google Chrome → Extensions → Configure the list of force-installed apps and extensions.
  3. Enable it and add the value below.
  4. Assign the profile to your user or device groups.
Value
ikhdemckhflgmlijkaomcpdmljegkakh;https://clients2.google.com/service/update2/crx
Windows Group PolicyActive Directory with the Chrome ADMX templates
  1. Open Computer Configuration → Administrative Templates → Google → Google Chrome → Extensions.
  2. Enable Configure the list of force-installed apps and extensions.
  3. Click Show and add the value below. Or set the registry key directly:
Registry
HKLM\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist
  "1" = "ikhdemckhflgmlijkaomcpdmljegkakh;https://clients2.google.com/service/update2/crx"
macOS (Jamf, Kandji, any MDM)Configuration profile for com.google.Chrome
  1. Add a custom settings payload for the preference domain com.google.Chrome.
  2. Deploy the key below to your Mac fleet.
Profile
<key>ExtensionInstallForcelist</key>
<array>
  <string>ikhdemckhflgmlijkaomcpdmljegkakh;https://clients2.google.com/service/update2/crx</string>
</array>

Check chrome://policy on a test machine to confirm the policy applied. To remove Screshot, delete it from the same policy. Keyboard shortcuts can be changed per person at chrome://extensions/shortcuts.

Questions about a security review or a rollout?

Email us at sales@screshot.com. Start with the review pack: it answers the usual questionnaire.