We have introduced a new report and API that allows customers to track attendance more granularly. The existing attendance report and API returns information about users who have joined a given scene. However, the private volume report and API will return information about users who entered a given private volume.
The term “private volume” often refers to any space providing privacy from the main space. Often, these are remarked by a blue border and an audible alert when a user enters and exits. For example, the offices, boardrooms, and end caps are private volumes in the workspace scene.
This report and API work with private volumes and their corresponding public volume. In other words, users can use this report to track who was in the main hallway of the workspace scene or the auditorium when private volumes are toggled off.
For customers to use this report, they need to understand the private volume ID(s) of the space(s) they are interested in.
At the moment, there is only one way to find this ID. Users must enter the private volume they are interested in and enter /roominfo in the chat.
Any user, from member on up, can use the /roominfo command.
The /roominfo command will return information about the private volume in the chat. Users should take note of any information that precedes the “voice IP” information - this contains the private volume information. This ID may or may not start with “PR-”. In the example below, the private volume ID is PR-2114767535--NewCampus.
Users can write down the private volume ID, copy the chat using the right mouse key, and then paste it into a document.
Private volume IDs stay consistent, so once you copy it down, it will remain the same in the future.
However, private volume IDs do differ among like scenes. For example, a boardroom in the workspace scene will have a different ID from other boardrooms in that same workspace scene and a different ID from other boardrooms in other workspace scenes.
Once the user has the private volume ID, they can access the “private space” report in the Virbela dashboard → analytics → private volume.
The user can set the start time and duration in hours (see the section below for details on the logic). They can search for a given private volume (entering the ID) or search across all private volumes within the campus.
The report will then return entries for every time a user was in the private volume for that time range.
The data range will return any users in the private volume during the indicated time frame.
In other words, consider the following users (a different scenario than above):
User A joined the private volume at 2:00 PM and left the private volume at 4:00 PM
User B joined the private volume at 2:45 PM and left the private volume at 3:15 PM
User C joined the private volume at 2:00 PM and left the private volume at 3:00 PM
User D joined the private volume at 3:00 PM and left the private volume at 4:00 PM
User E joined the private volume at 1:00 PM and left the private volume at 1:30 PM
User F joined the private volume at 4:30 PM and left the private volume at 5:00 PM
If the Start Time = 2:30 PM and the Duration = 1 hour, then the response will show Users A, B, C, and D as they all were in the private volume for some during the indicated time frame. Users E and F will not appear in the response.
Private spaces have their unique roles. While most private space users are campus members, they may have enhanced privileges in the private space. For example, a user can be a member of a campus but an administrator of a private space.
We resolved an issue where private space administrators were granted their campus role in the private space instead of their private space role. In other words, when an owner invited an administrator, the system would recognize them as a private space member instead. This is resolved.
Private space administrators are still invited as members of the campus. They will have administrator rights only in the specific private space.