PolicyBot in Google Slides

PolicyBot is the InPolicy reviewer for Google Slides. Share any deck with policybot@inpolicy.ai as a Commenter, and within about a minute it will:

• Drop an “I’m reviewing this deck” comment on the file as soon as it picks up the share, then update that same comment with the final summary when detection finishes.
• Add text-range anchored comments on phrases that may violate a policy — the highlight covers the exact words PolicyBot flagged, not just the whole shape.
• Render any proposed fix inline in the comment body as Suggested replacement: "…". Slides has no Suggesting mode equivalent, so this keeps the proposed change visible without a separate suggestion thread.
• Remove itself from the share list when it’s done — your security and privacy stay intact.

Sharing a deck with PolicyBot

1. Open the Google Slides deck you want reviewed.
2. Click Share in the top-right.
3. Add policybot@inpolicy.ai as a Commenter.
4. Click Send.

That’s it — PolicyBot picks up the share, posts its “I’m reviewing…” comment within a few seconds, and updates it with the final summary within about a minute.

What the summary comment tells you

Every reviewed deck gets one doc-top comment from PolicyBot. While the review is in flight the comment reads “I’m reviewing this document…”; once detection completes it updates to one of the outcomes below. The comment stays in the same thread the whole time, so you never see two doc-top comments for one review.

What we found	What the summary says
No InPolicy account for your company	PolicyBot didn’t find an account on your email’s domain and sends you to inpolicy.ai to sign up (the first user at every company is free).
Company has an account but you don’t	PolicyBot tells you the admin email to contact for access.
Your account exists but has no policies	PolicyBot tells you to reach out to help@inpolicy.ai to get a role on a Policy Area.
Reviewed, no violations found	PolicyBot confirms it ran against the policies you have access to and nothing crossed the confidence threshold.
Reviewed, violations found	PolicyBot lists each finding with policy name, severity, AI confidence, and a link to the policy, with text-range comments pointing at the relevant passage on each slide.

In every case, PolicyBot removes the deck from its own “Shared with me” after the review. For your security, you should also remove its access from the share dialog.

Reading the per-violation comments

Each per-violation comment is anchored to the exact text on the slide that tripped the policy. The comment body ends with two lines that show the actual rule and the metadata:

WARNING: This passage discloses an internal product roadmap to an external recipient.

— “No internal product roadmaps may be shared with external parties without explicit VP approval.” High severity · 87% confidence · https://app.inpolicy.ai/policies/conf-roadmap-1

When a policy calls for a rewrite or redaction, PolicyBot includes the proposed replacement inline at the top of the comment body:

Suggested replacement: “[REDACTED]”

Personal email addresses must be redacted before external sharing.

— “PII must not be disclosed in customer-facing communications.” Critical severity · 92% confidence · https://app.inpolicy.ai/policies/pii-1

The fields:

• Quoted rule — the exact policy text that flagged the passage, so you can judge the call without clicking through.
• Severity — Minor, Low, Medium, High, or Critical. Set per policy by your admin or Policy Lead.
• Confidence — how sure PolicyBot’s model is, from 0–100%. Each policy has a configurable threshold; below it, PolicyBot stays silent.
• Policy link — opens the policy detail page in InPolicy so you can read the full policy, severity rationale, and any examples.

Asking for another review

When PolicyBot finishes, it removes the deck from its own view and asks you to share it again if you want another pass. Re-sharing busts our review cache, so the next review picks up your latest changes — even if the deck body hasn’t changed since last time.

Re-sharing won’t duplicate prior comments. Before posting, PolicyBot checks the deck for its own open comments and skips any whose anchored passage and policy match a comment that’s still live. Closed (resolved or deleted) comments don’t count — if a finding is still relevant, PolicyBot re-flags it.

Privacy

PolicyBot only sees the decks you explicitly share with it. It uses the same policy-evaluation infrastructure as the rest of InPolicy and does not store your deck contents past the review window. See Privacy & data handling for the full data-handling policy.