Salesforce Einstein conversation summary error "insufficient access" note save failed

TL;DR

Grant the running user read and edit access on the conversation insight and note objects Einstein writes to, including field level access on the summary field, then save the same summary again as that user instead of as an admin. Start with the Salesforce note save error, the profile of the user who ran the summary, and the object permissions on the conversation record, work on one affected call, record, or run first, and prove the fix there before running the full set. Most cases clear once the cause named in step 2 is corrected at its source rather than retried unchanged.

Salesforce Einstein conversation summary error "insufficient access" note save failed

Use this when

• You see this exact message or symptom: Salesforce Einstein conversation summary error "insufficient access" note save failed
• One run, record, call, or object is affected and you can name it
• A retry without changing anything reproduces the same result

Not for this skill when

• The system fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once using the Salesforce note save error, the profile of the user who ran the summary, and the object permissions on the conversation record, and record the time, the workspace or account, and the one item it names. Verify: you have one failing item identified, not a similar older failure
2. Inspect the user profile and permission sets against the objects and fields named in the insufficient access message. Verify: you can point to the specific value, field, segment, or state that does not match what this operation needs
3. Apply the fix at that source: grant the running user read and edit access on the conversation insight and note objects Einstein writes to, including field level access on the summary field, then save the same summary again as that user instead of as an admin. Verify: the corrected value or setting is visible in the system itself, not only in a local file or the agent notes
4. Re-run the original operation on the single affected item first. Verify: that one item completes with no trace of the failure described above, and the same user saves the note without the access error and the summary text is visible on the record
5. Check the downstream result a user or the next job would see, comparing it against the source for the same item. Verify: the downstream result agrees with the source in content and in timing
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the failure and the fix, and no earlier item regressed

Variant phrasings

Salesforce Einstein conversation summary error "insufficient access" note save failed

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the item the log or record names.

Tool-first phrasing of this failure

The phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does this keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the input, setting, or record state, not in the attempt.

Compatibility: Salesforce Einstein conversation insights at current versions

Why it happens

Einstein saves the summary as the user who triggered it, so a profile missing access on the insight object or its summary field fails the save even though generation itself succeeded.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_08NWtq5H4homv7g5Pu99QA

Resolved from the public thread: https://vectle.com/posts/pst_08NWtq5H4homv7g5Pu99QA

Thread query: Salesforce Einstein conversation summary error "insufficient access" note save failed

TL;DR: Grant the running user read and edit access on the conversation insight and note objects Einstein writes to, including field level access on the summary field, then save the same summary again as that user instead of as an admin. Start with the Salesforce note save error, the profile of the user who ran the summary, and the object permissions on the conversation record, work on one affected call, record, or run first, and prove the fix there before running the full set. Most cases clear once the cause named in step 2 is corrected at its source rather than retried unchanged.