In the dynamic landscape of virtual communication, Digital Samba has emerged as a prominent solution for seamless video conferencing and online meetings. Leveraging its developer API, you can now take control of your virtual spaces to enhance user experience and tailor settings according to your unique requirements.
In this article, we’ll delve into configuring room defaults in Digital Samba, and shed light on the significance of room inheritance, how to configure specific rooms, and ultimately, empowering users to optimise their virtual interactions.
Table of Contents
Before delving into the specifics of room defaults, it's crucial to grasp the concept of room inheritance.
Digital Samba employs a hierarchical structure, where settings configured at a global scale (default room settings) are automatically inherited by individual rooms unless you configure the individual room specifically. This approach ensures consistency and efficiency by allowing users to define defaults inherited by individual rooms.
So, for instance, if you create a new room and don’t tweak its primary colour or background colour, and then a team admin or moderator changes the primary colour to green in the default settings, your new room’s primary will automatically be altered to green.
Let’s explore how this works when configuring your room using the developer API.
To harness the full potential of the Digital Samba developer API, you can take a more granular approach to configure your room by customising settings for individual rooms.
You have two options for configuring your Digital Samba room:
Start by making a POST request to the /rooms endpoint. This method is used to set up your room's configuration during its creation. The highlighted section shows the room configurations you set when you create the room
Alternatively, you can execute a PATCH request to the /rooms/:id endpoint. This approach is useful when you need to modify the settings of an existing room. Simply provide the id of the room you want to edit and the changes will be applied accordingly.
Important: Do not leak your developer key into the client’s browsers. Execute these requests only from your backend (server-side). Note you must do a base64 encoding of the: concatenation of your teamId and developer key, but this is out of the scope of the article. Every major language provides built-in functions to base64 encode data.
Please ensure you have the API credentials for authentication before executing the PATCH request. This involves adding your team_id and developer_key, which you can access in the dashboard’s ‘Team’ option, as shown below.
To edit a room, add the fields you want to configure in the data parenthesis.
For example, if you are holding a lecture or training course, turn off screen sharing for attendees. Even if you've enabled screen sharing in your default room settings using the developer API, it’ll be turned off for this specific room. You might also want to enable the chat feature and ensure the UI is in English.
Let’s see how this looks with a PATCH request code example. We will use JavaScript, but Digital Samba allows you to achieve the same with PHP, bash, or Java. Explore more here.
The fetch() function will make a request to the API to update that specific room with the new settings included in the PATCH request, as such, updating the room.
While configuring specific rooms provides tailored solutions, room defaults are your foundation for consistency across multiple rooms. Setting defaults saves time and maintains a standardised experience for users.
Unlike configuring a specific room, you must execute a PATCH request against the /api/v1 endpoint, as highlighted below.
For example, suppose your goal is to ensure a uniform brand identity throughout your video conferences. In that case, you can achieve this by implementing the following settings: a top bar, a right-positioned toolbar with a green colour scheme, utilising green as the primary colour, incorporating a white background, prominently displaying your logo, maintaining an English-language user interface, and fortifying security across all rooms through the activation of end-to-end encryption (E2EE).
As mentioned above, the main difference between configuring a specific room and updating your default room settings is the endpoint to which you execute the PATCH request.
With the Digital Samba video conferencing API, you can update as many fields for your default rooms as you wish. See our documentation for a more detailed list of the fields you can configure.
Configuring room defaults using the developer API in Digital Samba marks a transformative step towards enhancing virtual interactions. By embracing the concepts of room inheritance and targeted configurations, you can create a virtual environment that aligns seamlessly with their needs.
Get started today with a free account.