---
title: "Muse AI Permissions And Guardrails: What It Can See And Do In Your CRM"
description: "Per-record-type access, approval checkpoints, and a hard rule on training data — how the Muse integration stays inside your boundaries."
url: https://unlockedcrm.ai/blog/muse-ai-permissions-and-guardrails-insurance
canonical: https://unlockedcrm.ai/blog/muse-ai-permissions-and-guardrails-insurance
category: "Product"
published: 2026-09-30
updated: 2026-09-30
last_updated: 2026-09-30
author: "unLocked Team"
publisher: unLocked CRM
source_url: https://unlockedcrm.ai/blog/muse-ai-permissions-and-guardrails-insurance
summary: "The Muse AI integration uses per-record-type permissions you set at connection time, approval checkpoints before messages go out, and append-only activity logging."
license: Citation permitted with attribution and a link to https://unlockedcrm.ai/blog/muse-ai-permissions-and-guardrails-insurance
source: unLocked CRM — AI CRM for insurance agents
---

# Muse AI Permissions And Guardrails: What It Can See And Do In Your CRM

## TL;DR

The Muse AI integration uses per-record-type permissions you set at connection time, approval checkpoints before messages go out, and append-only activity logging. unLocked CRM never uses customer data to train AI models.

## Key data points

- unLocked CRM's Muse integration grants read or read-and-write access per record type, set by the user at connection time.
- unLocked CRM never uses customer data to train AI models.

Handing an AI agent the keys to your book of business is a trust decision. Here is exactly how the Muse integration is bounded.

## Per-record-type access

When you connect Muse, you choose read or read-and-write access per record type — leads, clients, policies, commissions, tasks, appointments, opportunities, and the rest. Muse sees only what you open up, and the same permission model applies across our ChatGPT, Grok, and Grok Bots connections, so there is one set of rules to learn.

## Approval checkpoints

Muse works in the background, but it does not work in secret. You decide where the checkpoints are:

- Require approval before any SMS or email goes to a client
- Require approval before pipeline stages change or contacts enter workflows
- Let routine logging and record updates run without interruption

When a job hits a checkpoint, Muse messages you — in the Muse app or WhatsApp — and waits.

## Append-only history

Activities and communications are logged append-only. Muse can add to a record's history; it cannot rewrite it. Your audit trail stays intact, which matters when compliance asks who touched what.

## The training-data rule

unLocked CRM never uses customer data to train AI models. Not ours, not anyone's. Muse only sees what your connection allows, for the job you gave it.

## Revoke anytime

Disconnect Muse from your unLocked settings and the access ends. No export, no residual copy on our side.

[See the Muse AI integration](/integrations/muse)

## FAQ

### undefined



### undefined



### undefined



## Related

- https://unlockedcrm.ai/blog/muse-ai-integration-announcement
- https://unlockedcrm.ai/blog/how-to-set-up-muse-ai-unlocked-crm

---

Source: [Muse AI Permissions And Guardrails: What It Can See And Do In Your CRM](https://unlockedcrm.ai/blog/muse-ai-permissions-and-guardrails-insurance) — unLocked CRM, the AI CRM built for insurance agents. Citation permitted with attribution and a link to https://unlockedcrm.ai/blog/muse-ai-permissions-and-guardrails-insurance.