Overview of the Real-time Collaboration configuration options
List of all available RTC configuration options.Contribute to this page
The Real-time Collaboration (RTC) plugin uses promise-based “provider” functions to support a variety of configuration scenarios including asynchronously fetching data from a server. Function input parameters are provided as an object, allowing unused fields to be omitted.
These options are required when using the Real-time Collaboration (RTC) plugin.
- Provide a unique identifier for current document (editor content).
- Provide the editor with encryption details for encrypting the content before it is shared between collaborators.
- Provide the editor with a JSON Web Token (JWT) for verifying that the user has access to edit the current document.
These options are assist with improving the user experience. They are not required, but are recommended.
- Assists with communitcating to the end-user that either:
- They have been unsuccessful in connecting to the collaboration session.
- They have lost their connection to the collaboration session.
- This option:
- Allows the user’s name or an alias to be shown on user “carets” in collaborative sessions, and
- Assists with providing data for:
The following options assist with integrating Real-time Collaboration and improving the user experience.
- Assists with autosaving the editor content during a RTC session.
- Assists with adding initial content for a newly created (initialized) editor.
- Allows additional user details to be provided for:
- Assists with notifying users that collaborators have joined a RTC session and can be used to maintain a list of connected users.
- Assists with notifying users that collaborators have left a RTC session and can be used to update a list of connected users.
- Allows integrators (developers) to disable the unsupported content notification.
Thanks for the feedback!
Can't find what you're looking for? Let us know.