---
isPublished: true
template: "page.peb"
title: "Control Access to Experience Rooms"
displayName: "Control Experience Room Access"
description: "Save and publish an Experience, pause Room access, disable a member, and close a Room after signing."
category: "support"
contentType: "guide"
audience: "admin,developer"
tags: "salesforce,experiences,rooms,access,flow,esignature,revocation"
section: "support"
seoTitle: "Control Experience Room Access | DialogueOne"
seoDescription: "Control published Experience content, recipient access, unavailable messages, and Room closure with Salesforce Flow."
llms: true
llmsSection: "Build Developer"
llmsTitle: "Control Experience Room Access"
llmsDescription: "Admin controls for Room, member, and item access; access timing; unavailable messages; and a document-signing completion Flow."
llmsOptional: false
llmsOrder: 32
---

Use Salesforce records to control an Experience Room.
Keep draft changes private. Publish approved content for recipients.
Use access fields to pause the Room or disable one member.

## Before you start

- Give the administrator or running Flow user the required record and field Edit access.
- Identify the exact Room, member, or item that the change must affect.
- Test with a recipient invitation and a test record before you change a customer Room.
- Review [XP Access and Permissions](/support/xp-permissions.html).

Subscriber API names usually include `rooms__`.
The records are `rooms__DocumentRoom__c`, `rooms__DocumentRoomMember__c`, and `rooms__DocumentRoomItem__c`.

## Save a draft or publish content

**Save draft** saves work for the author. It does not replace the content that recipients see.
A draft can contain new items, different navigation, and changed recipient assignments.
These changes apply when publication succeeds.

**Publish** makes the approved version available to its selected recipients.
The existing invitation opens the latest published version of the same Room when the recipient remains authorized.
You do not need to send another invitation only because the Room content changed.
Invitation expiry and access limits still apply.

Builder shows **Draft**, **Published**, or **Unpublished changes**.
Room availability is separate from this authoring state.
Publishing content does not reopen a Room that an administrator disabled.

An explicit historical version link continues to show that version.
Room and member access controls still apply to it.
To stop access to all versions, disable the Room or the member.

Previously published links retain their original invitation rules. Historical content and signing evidence are retained.
The stable-link behavior applies after the administrator enables the updated publication controls for the Room.
Older Rooms that have not been updated keep their existing behavior.

## Required permissions

| Work | Required access |
| --- | --- |
| Pause, reopen, or retire a Room | Edit the Room record and its activity/archive fields. |
| Set the unavailable message | Edit the Room record and its unavailable-message field. |
| Disable one recipient | Edit the Member record and its activity field. |
| Exclude one item from the next publication | Edit the Item record and publish the Experience. |
| Configure Experience data context | Admin authority on the Experience template and access to its Data Context Definition. |

Use record sharing and field-level security to limit these controls.
A visible record does not by itself permit editing or publishing.

## Access controls

| Control | Result |
| --- | --- |
| Room `rooms__IsActive__c = false` | Pause entry and later operations for all recipients. |
| Room `rooms__IsArchived__c = true` | Retire the Room and prevent entry and later operations. |
| Member `rooms__IsActive__c = false` | Disable that recipient. Other members keep their access. |
| Item `rooms__IsActive__c = false` | Exclude the item from the next successful publication. |
| Item `rooms__IsArchived__c = true` | Exclude the item from the next successful publication. |
| `rooms__Status__c` and other status labels | Describe business progress. A status label alone does not revoke access. |

An item change does not remove the item from an existing historical version.
Save or remove an item in the draft, then publish to change the current Experience.
The new publication omits an excluded item's content, navigation, Actions, and download controls.
Other permitted items remain available.

Use Room or Member controls when you must stop access without publishing content.
Do not use inactive Items as draft staging.

## When a change takes effect

An access change is sent after Salesforce saves the transaction.
This applies to record edits, Flow, and other authorized record updates.
If delivery is unavailable, the last confirmed access state remains in use.
Review the existing error logs. Use the **Resync Experience Access** Flow action with the Room ID to retry a failed update.

Each new Room open or reload checks the confirmed access state before content is shown.
A forwarded invitation and another browser session follow the same check and existing invitation rules.
Submitted Actions and each chat turn also check access.

The Room does not check access on a timer.
An open page keeps content that it has already displayed.
An operation denial does not erase the document or conversation that the user has already seen.

## Set an unavailable message

To set a default for new Rooms, open a Secure Room template in Experience Builder. Under **Type → Room access**,
enter a **Room unavailable message**, then save and publish the template. Each new Room receives a copy from the
published template. Changing the template default applies to Rooms created after the next publication.

To change one Room, edit **Room Unavailable Message** (`rooms__RoomUnavailableMessage__c`) on its Salesforce record.
The Room field takes effect without a content republish. Clear it to use the standard message. Both settings support
**2,048 characters** of plain text.

For example:

> This quote is being updated. Please contact your account representative for help.

An authorized recipient sees this message when the Room is inactive or archived.
If the field is blank or absent, the message is:

> This room has been closed by the Publisher.

Formatting tags display as text. Do not put confidential information in the message.
An invalid session or a disabled member receives a generic access message.

## Create and share an Experience

1. Generate and check the document.
2. Create the Experience with Flow, or prepare and publish it in Experience Builder.
3. Check the Success result before you send a link.
4. Send the recipient's invitation link with the existing Salesforce email action.
5. Confirm that the recipient can review the content and use the assigned signing controls.

Use the [quote generation and eSignature Flow guide](/support/automate-salesforce-quote-generation-esignature.html)
for the complete creation example.

```mermaid
flowchart TD
    A[Generate and check the document] --> B{Creation method?}
    B -- Flow --> C[Create Experience]
    B -- Builder --> D[Prepare and publish Experience]
    C --> E{Success?}
    D --> E
    E -- No --> F[Handle the error before sending]
    E -- Yes --> G[Send the recipient invitation]
    G --> H[Recipient reviews and signs]
```

## Pause a Room while you correct a quote

1. Open the exact Room record for the incorrect quote.
2. Set `rooms__IsActive__c` to false.
3. Open the invitation in a new browser session. Confirm that access is blocked.
4. Correct and approve the draft quote and Experience.
5. Publish the corrected content to the same Room.
6. Explicitly reopen the Room when the correction is ready.
7. Use the existing invitation to confirm that it opens the latest published content.

A publication does not remove an administrator's access hold.

```mermaid
flowchart TD
    A[Incorrect quote was shared] --> B[Set the Room inactive]
    B --> C[Verify denied entry]
    C --> D[Correct and approve the draft]
    D --> E[Publish to the same Room]
    E --> F[Explicitly reopen the Room]
    F --> G[Use the existing invitation]
```

## Reopen a Room or enable a member

1. Set the Room's `rooms__IsArchived__c` to false if it was archived.
2. Set the Room's `rooms__IsActive__c` to true.
3. Set the required Member's `rooms__IsActive__c` to true if that member was disabled.
4. Confirm that the member belongs to the selected publication.
5. Test with a valid invitation after the access update completes.

Reopening does not extend an expired invitation or add a recipient to a publication.
A new recipient must be included in a successful publication before using that content.

## Data context and live components

An administrator selects the Data Context Definition on the Experience template.
The instance uses the inherited selection. Users cannot override it on the instance or through Flow.
Published content keeps its approved data definition. Its permitted business data can be read when the Room opens.

The document template's merge definition is separate from the Experience template's live-data definition.
Opening a Room does not regenerate the quoted document or its PDF.

If current business data is unavailable, the affected Checklist or Interactive Content shows a local unavailable message.
Unrelated published content remains usable. Unavailable operations are disabled.
The Room does not substitute stale business data without telling the user.

## Close a Room after required signing is complete

Use a platform event-triggered Flow for **DialogueOne Platform Event** (`rooms__Event__e`).
Handle **`DOCUMENT_ESIGNED`** from the **`XP_NATIVE_ESIGN`** source.

This event represents one signer transaction. It does not by itself mean that all required signers have finished.

1. Get the exact Room identified by `rooms__RoomId__c`.
2. Confirm the required business completion condition for that Room and its documents.
3. If signers remain, leave the Room available for them.
4. Update the related Opportunity, such as setting its stage to Closed Won.
5. Set the Room's `rooms__IsActive__c` to false, or archive it when it must be retired.
6. Handle repeated events without repeating completed business work.
7. Use Flow Fault paths to report failed business updates.

The event also identifies the Room Item and Member. Use these fields to confirm the correct transaction.
Do not select an unrelated Room only because it belongs to the same Opportunity.

```mermaid
flowchart TD
    A[DOCUMENT_ESIGNED event] --> B[Find the exact Room and Opportunity]
    B --> C{Required signing and business work complete?}
    C -- No --> D[Keep access for remaining work]
    C -- Yes --> E[Update the Opportunity]
    E --> F[Disable or archive the Room]
```

The existing **Close a Document Room** action is archive-oriented.
Use the activity field for a temporary hold.

Room closure can prevent later status refreshes and new download requests.
If recipients must return to download a signed document, keep the Room and those members active.
Signing alone must not be treated as an instruction to disable the Room.

See the [Platform Event reference](/support/events/index.html) and [event types](/support/events/types.html).

## File-access limits

These controls cannot recall a downloaded file or content already displayed in an open page.
Previously issued file access keeps its existing access period.
Room closure does not invalidate all previously issued file links or remove saved copies.

## Troubleshooting

| Symptom | Check |
| --- | --- |
| Draft content is absent from the customer view | Confirm that the changed draft was successfully published. |
| A tab is missing after publication | Check draft membership and the Item activity/archive fields. |
| A previously emailed link shows older content | Confirm the latest publication succeeded and the Room uses stable-link controls. |
| A historical link shows older content | This is expected. Use the invitation for the latest published version. |
| One recipient is denied | Check Member activity, publication membership, invitation expiry, and access limits. |
| A status says Closed but entry still works | Set a Boolean access control. Status text alone does not revoke access. |
| An access edit has not arrived | Check synchronization errors. Run **Resync Experience Access** with the Room ID. |
| A live component is unavailable | Check its data access and business records. Static content can remain available. |
| Signed content becomes unavailable after a Flow | Check whether the Flow disabled or archived the Room or Member. |

For new controls, test original and forwarded invitations, reload, another browser, explicit reopening, and operation denial.
Also test the final signature, remaining signers, repeated events, and Flow Fault paths.
