Explicit Recording mode allows hosts to obtain recording consent from all guests. This guide is designed for Jiminny Admins to setup and configure this advanced mode.
Prerequisites
Please ensure your Jiminny instance has the feature enabled. You can find out by checking if "Explicit Consent" is an option in your Organization Recording Settings. If not, please ask Support or your Account Manager for access.
Your Microsoft Admin will need to install the Outlook Add-in for your team and follow our guide.
In Jiminny Organization Settings, toggle on Explicit Consent as above.
Meeting Flow
When Strict Consent is enabled, your team will need to add Jiminny links to their meetings when creating them in the calendar event. They should not add their meeting provider links to the event. Behind the scenes, Jiminny will create these on their behalf. The invite should be sent out as normal.
When joining the meeting, all participants will click through the Jiminny consent link. The consent page will ask for permission to record the meeting. Regardless of their choice, Jiminny will track this and forward them directly to the meeting.
If any participant chooses to not be recorded, the meeting will not recorded and the host will receive an email notification.
Setting up Meetings
Create your calendar event as normal, and ensure you click the Jiminny button in Outlook, and not add any other meeting links e.g. Teams meeting. Select Add a Jiminny Meeting. On first run, you will be asked to select your Jiminny Data Region- this is where you log in to Jiminny.
When it comes to joining the meeting, all participants will click through to a consent page. This page will store the recording preference and take them to the meeting.
Notes
Once enabled, meeting recording will become locked down to ensure strict compliance.
If a host creates a meeting without adding a Jiminny consent link, it will not be recorded. However the host will receive an email notification letting them know.
This applies to all users of your Jiminny instance with a Recording seat, regardless if the meeting provider supports Jiminny consent links (currently only Microsoft Teams is supported).
All participants of the meeting must access the Consent page (and therefore opt-in or out of recording) to join the meeting.
Viewing Compliance Information in CSV Exports
Customers using the "Explicit Recording Consent" add-on can now export compliance information from Team Insights → Conversations. This helps managers and compliance teams understand whether meetings followed the required consent process and whether participants agreed to recording.
These additional columns are only available for customers with "Explicit Recording Consent" enabled.
Column | What it shows | Example |
Compliant | Whether the meeting was created using the Jiminny calendar add-on and went through the Jiminny consent flow | Yes / No |
Consent | Whether participants accepted or declined recording in the format: IP:C; IP:NC (The IP represents the participant’s IP address because it’s the only reliable information available during the consent flow) | 192.168.1.10:C 192.168.1.11:NC |
External | Whether the meeting was external or internal | Yes / No |
What does “Compliant” mean?
A meeting is marked as Compliant = Yes when it was created using the Jiminny calendar add-on, and participants joined through the Jiminny consent page before entering the meeting. This means the required consent process was completed.
A meeting is marked as Compliant = No when the meeting was created without the Jiminny add-on, or participants did not go through the consent page.
Note: Consent & compliance data is only available for conversations from the current calendar year.