Session Recording (Beta)
We now offer Session Recording (currently in Beta), which allows you to keep a video archive of important sessions for future reference or evaluation, or to conform with strict compliance and privacy rules.
These will be high quality video archives of everything you do within a session. Masked information stays masked in the archives and as always, Surfly will not store this information but only transfer it to the location defined by you.
At the moment this feature is available on demand.
If you are interested in using this feature, please contact us at firstname.lastname@example.org. We will turn it on for you and then you will be able to set up archiving to your storage.
HOW IT WORKS
Session Recording feature is automated - once set up correctly, it will start by itself at the start of the session, and end when the session is completed.
Turning it on per session, as opposed to turning it on for all sessions, is possible via our APIs. When starting a session using APIs you can pass on the necessary session options.
Additionally, if you are using the admission option, a host can choose to Admit or Dismiss the Session Recorder entry into the session, hence deciding if the session will be recorded or not, after starting the session.
Steps for setup
Once the feature is made available to you, the options related to setting it up will be enabled.
These are the steps for activating Session Recording:
automated_session_recording_enabled(Dashboard Settings > Options > Session Functionality)
s3_access_secret(Dashboard Settings > Options > Company Settings)
s3_recordings_bucket(Dashboard Settings > Options > Session Functionality)
Recording will not work with option
private_session: true. Please set it to
false if you are planning to use session recorder.
During the session
Session recording is created from the perspective of a following-participant. You will see an indication on the top bar that the session is being recorded:
or in bottom bar in case of mobile devices:
Video files (.mkv) will be stored in the S3-compatible bucket that you have specified. Video files will be named after the session ID. Surfly does not have access to them.
The folder structure in this bucket follows below convention:
For example, if someone is logged in as
app.surfly.comand records a session, that recording will be available at:
Also, depending on the user flow used, it's possible that the
agent_emailis not passed to the session, so for those cases, the recordings will be at: