Prism DLP partner kit: start here
For whoever sets Prism up at your organisation (IT, security or the Jamf/Google admin). Everything here is also in the Prism console under Set up and Integrations, with your API URL and keys filled in.
Order to follow
- Sign in to the console (https://app.prism-dlp.com) with the invitation we sent. Under Settings, leave the mode on Observe for the first week: Prism records what it would do without blocking anyone.
- Tell your staff what Prism checks and why, and link the privacy policy (https://prism-dlp.com/privacy). A template is in
staff-notice.md. - Browsers (Chrome and Edge):
chrome-extension-rollout.md. On Macs with Jamf:jamf/README.md. - Macs (desktop AI apps, AI command-line tools, copies to USB and cloud folders):
jamf/macos-agent.md. - Choose your AI tools under Destinations: approve, check or block each one, mark tools as work-accounts-only, and read each tool’s risk notes.
- Connect your SIEM and chat (optional):
integrations.md, also at https://prism-dlp.com/docs/integrations. - After a week, review Incidents with us, adjust detectors and destinations, then switch to Coach (warn) or Block. Use Exceptions for one-off needs rather than loosening policy for everyone.
Reference
| Guide | For |
|---|---|
chrome-extension-rollout.md |
Force-installing and configuring the browser extension (Google Admin, macOS, Windows), closing gaps, checking it worked, what it sends |
jamf/README.md |
The extension through Jamf Pro: the four files and two profiles |
jamf/macos-agent.md |
The Mac agent through Jamf Pro: package, settings, permissions, keeping it on |
integrations.md |
Slack, Teams, Splunk, webhooks, the Events API and Microsoft Sentinel |
staff-notice.md |
A notice to send staff before rollout |
| https://prism-dlp.com/privacy | What the extension collects and how it’s used |
Updated 9 October 2026