1 vote
Can we please get a new security option on entries to control who can view/access recordings of sessions? We want to record sessions but only allow senior management to be able to view those session recordings for privacy reasons.
ad2061cb-30ab-481d-8424-dca9eda6a6c2.png
Hello,
Thank you for your suggestion. We don't have a specific permission on entries, but we have one top level available in System permissions. Is it something that could work for you ?
Best regards,
François Dubois
500d65ac-2d6e-4b1a-a22c-89e81a481d90.png
I did look at this, but my understanding is that this controls whether session recording is available at all. We want ALL sessions to be recorded, we just want to restrict who can access/view the recordings once they are made.
If you had an additional setting in this section to control the ability to "view" recordings, then that would meet our needs.
I'm no developer, and I'm sure it's more complicated than first thought, but just need something to hide these tab/options - I believe this is the only way to view recordings through UI and RDM.

b2dd194d-f931-4e07-b17b-6640434761d1.png
a6e35213-fa8c-4b8f-9a91-192a3e4bc3ba.png
284bae4a-7d26-43bb-af37-7d271abb385e.png
Hello,
I think there is a misunderstanding, sorry for confusion. The Recording tab will be available if you are an administrator or if you have the Session Recording permission that I showed in my previous message. Even if the Recording tab is not there for a user, the recording will still be made. Conclusion: The session recording permission is used to be able to see or not the recording, not to allow or not the recording itself. Is it clearer ?
Best regards,
François Dubois
Hi Francois,
Right you are - that setting does exactly what we want it to do. Perhaps could be renamed to "Access Session Recordings" to make it more obvious.
Thanks for your help.
Hello sjames,
You’re not the first to mention that this part can be a bit confusing, and we completely get it. Thanks for pointing it out, it’ll be taken into consideration as I’m working on the fix right now.
Best regards,
Jeremie
Hello,
This issue has been implemented and will be available in our version 2025.3.5.0 or higher.
Thank you for your patience.
Best regards,
Marc-Andre Bouchard