Skip to content
Platform / Data protection

Data protection

Close risky sharing. Keep collaboration open.

Find exposed documents and sensitive content across your connected applications. Bring in the people who know why something was shared, then help them resolve the exposure.

Google DriveSharing
Financial forecast.xlsx
SensitivityFinancial data
AccessAnyone with the link
OwnerAlex Martin
Alex removed the public link.
Illustrative example · controls depend on your configuration

Trusted by 190+ organizations

Whisper AeroGreenlyWelcome to the JungleResilienceDalma

Sharing moves faster than permission reviews.

A public link outlives a project. An external collaborator keeps access. Sensitive information lands in a channel. Elba connects those exposures to the asset, its audience, and the person who can help resolve them.

01

Focus on the exposure that matters.

Explore public, personal, and professional sharing. Use sensitivity categories and available risk analysis to decide which findings deserve attention first.

02

Bring business context into the decision.

Send an issue to the employee who owns the context. Let them review permissions, correct unnecessary sharing, or keep legitimate access with a recorded outcome.

03

Make repeatable fixes easier.

Configure Playbooks around sharing, sensitivity, risk, or age. Distribute matching issues and automate remediation where the connected application supports it.

From visibility to action

From an exposed file to a clear outcome.

Keep the finding, the decision, and the follow-up connected.

01

Find the exposure.

Connect a source and review its findings. See the asset, sharing audience, owner, and available sensitivity or risk context together.

02

Choose how to act.

Review the issue yourself or distribute it to an employee. Use a Playbook when a recurring pattern has a clear response.

03

Track what changed.

Remove sharing permissions or delete an asset where the source allows it. Follow corrections and accepted exceptions, with outstanding work still visible.

A concrete demo scenario

Review one Google Drive recipient before removing access.

Choose an address or exact domain, examine the recorded sharing, and preview eligible changes on selected files. Agree an approved demonstration scenario with our team; your production files do not need to be changed.

  • Inspect recipients, files and observation dates together. Recorded sharing can be incomplete or old; check the source and coverage before deciding.
  • Select up to 100 Google Drive files. Preview the matching direct external user or domain grants, other grants retained, and files that could not be checked.
  • Confirm the eligible selection deliberately, then inspect removed, already absent, failed and unknown results. Other recipients’ grants stay outside this manual action.
  • Choose the appropriate workflow: this selected-recipient action, a separate employee review, or a Playbook. The Google Drive Remove sharing Playbook acts on the whole file.
Meet the employee experience

Your tools. A connected view.

Make your stack part of the solution.

A closer look

The questions that matter.

Which applications does Data Protection cover?

Sources include Google Workspace, Slack, Microsoft Teams, SharePoint, OneDrive, Dropbox, and Confluence. Detection and available actions vary by connection and asset type.

Can Elba fix every sharing issue automatically?

Direct fixes depend on the source and asset. Elba offers supported permission removal or deletion; other changes happen in the source application. Connecting a source does not activate remediation.

Does Slack coverage include private conversations?

The current Slack Data Protection connection analyzes supported public-channel messages available to the authorized connection. Its permissions do not grant private-channel history access.

Can I remove only one recipient’s Google Drive access?

An Elba organization owner or administrator can select up to 100 files, preview matching direct external user or domain grants, and confirm eligible changes. This manual action preserves other recipients’ grants. Inherited, group, owner, public-link and internal access, and folders, are excluded. Results distinguish removed, already absent, failed and unknown grants; inspect remaining access paths in Google Drive.

Is the selected-recipient action the same as a Playbook?

The Google Drive Remove sharing Playbook applies to the whole file. The manual selected-recipient action previews a bounded set of direct grants for an address or exact domain. A domain selection includes that domain’s addresses and whole-domain grants, without subdomains. Keep these scopes separate, and review source coverage and current permissions before acting.

Connected by design

One risk rarely lives alone.

Bring one sharing decision to your demo.

Follow a representative Google Drive case from recorded exposure to a permission preview and dated results. Compare the manual action with employee review and Playbooks, including what each leaves for source-side work.

See a sharing review