Use permission sets to control the features in Document Builder and Experience Builder. Use the parent business record, such as a Quote, to control approval before sending.
Records and feature permissions
| Content | Salesforce object |
|---|---|
| Document templates and generated documents | Content__c |
| Experience templates and generated Experiences | DocumentRoom__c |
| Experience items, members and review requests | DocumentRoomItem__c, DocumentRoomMember__c, RoomRequest__c |
Subscriber object and field names usually include rooms__. Salesforce calls the object Update permission Edit. This page uses Update (Edit) for that permission.
| Permission setting | Builder behavior |
|---|---|
| Read | View content within the configured Builder scope, including the template library. |
Create on Content__c |
Generate documents from published templates. |
Create on DocumentRoom__c |
Create Experiences from published templates. |
Update (Edit) on Content__c |
Edit eligible document instances in Document Builder. |
Update (Edit) on DocumentRoom__c |
Edit eligible Experience instances in Experience Builder. |
| Update (Edit) | Archive or restore eligible instances with the Builder controls. |
| Delete | Use the delete action, subject to retention rules. Archive does not require Delete. |
| Publisher or Admin library authority | Create, edit, publish and archive templates. Instance Update alone does not enable library management. |
Access to a Builder allows users to view its managed records within the configured scope. The same feature permissions apply to manual actions and Flow actions. Viewing a record does not enable editing, approval or sending.
Each generated document has one Content record. Edits update that record; they do not create a record for each version. Saving a PDF to the business record updates its File and version references. Previewing or downloading a PDF does not create a Content record.
Three permission sets
| Permission set | Instance features | Library features | Administration |
|---|---|---|---|
| XP User | View, generate, edit and archive eligible documents and Experiences. | View and use published templates. | None. |
| XP Publisher | XP User features. | Create, maintain and publish templates. | None. |
| XP Admin | Required content administration. | Full library management. | Configure access and repair content records. |
Clone these sets or create custom sets for your teams. For a read-only user, omit Create, Update and Delete. Permissions combine across profiles and permission sets. A restrictive set does not remove another set's grants. Include the required class, field, related-record and File access.
Content roles and library access
| Content role | Allowed work |
|---|---|
| Viewer | View and preview content within the assigned scope. |
| Author | Generate and personalize document and Experience instances. |
| Publisher | Author work plus template and library management. |
| Admin | Content administration, library management and configuration. |
| Signer | Sign the assigned document fields in the assigned recipient package. |
Content roles describe allowed work. They do not require a separate permission set for each role. Signer access does not grant authoring or business-approval authority.
Library management is available to Publishers and Admins. A user who can edit instances can still have read-only access to the library. Opening the library directly does not change that access. These restrictions apply to each save, publication and archive action.
flowchart TD
A[Open a Builder] --> B[View content and templates]
B --> C{Allowed action?}
C -- Create --> D[Generate an instance]
C -- Update --> E[Edit an eligible instance]
C -- Publisher or Admin --> F[Manage the template library]
Use the Builder controls to change content and archive state. Keep document identity, version, approval and File-reference fields protected from direct edits. Document archive keeps records and history. It does not revoke existing invitations. Use Room access controls to pause a Room or disable a member. Save draft changes for authors. Publish to change the recipient experience, including item exclusion. After stable-link controls are enabled, the existing invitation opens the latest authorized publication. Explicit version links retain historical content and still respect Room and Member access controls. An administrator configures the Experience template Data Context Definition; instances inherit that selection. View All Records, Modify All Records and View All Fields retain their Salesforce meanings. They do not replace the library-management permission.
Parent-record approval
Configure an Approval Process or a controlled Flow on the Quote or other parent record. That process selects approvers and defines allowed exceptions. No separate XP Approver permission set is required. An editable Approved picklist alone is insufficient.
Approval covers the reviewed business data, exact document/PDF versions and Experience contents. Changes to that package require approval again when the parent process requires it. Keep the previous approved package and its history. Publisher and Admin access does not bypass approval. Record any exception through the parent process.
flowchart TD
A[Generate and personalize] --> B{Approval required?}
B -- Yes --> C[Approve the parent record and exact content package]
C --> D[Send]
B -- No or authorized exception --> D
D --> E[Submit recipient email and record the result]
Send contract
Send submits an email for a specific recipient, with the fixed Experience link and approved attachments. Enable Enhanced Email and the required email logging before using Send. Manual and Flow delivery use the same approval and recipient rules.
| Status or record | Meaning |
|---|---|
| Approved or exempt | The parent process permits sending this exact content package. |
| Sent | Salesforce accepted the email submission for that recipient and the sending transaction committed. |
EmailMessage |
The related email activity. Creating activity alone does not prove that email was sent. |
| Delivered or opened | Separate observed events. Sent does not confirm either event. |
A Viewer can send an eligible package when Send is enabled for that user. Editing content or managing templates is not required to send approved content. Preparing a link or copying it does not mean Sent. A live recipient link follows the same release rules.
Record the sender, recipient, parent record, content version, approval or exception, time and result. Report failed or uncertain sends. Repair missing email activity without sending the email again. Confirm an uncertain result before retrying. Update a Quote's Sent stage only after sending is confirmed. Show delivery and Room activity separately from that stage.
Configure permissions with a coding agent
Give your agent this permission reference. It is also listed in llms.txt and the coding-agent guide.
Review my authorized Salesforce metadata and effective permissions. Use this reference to draft access for my users and required actions. Keep library management separate from instance editing. Preserve protected content fields and parent approval. Show the permission changes and validation plan before applying them.