Skip to main content

Permissions

Guide to managing consent, privacy, recording notifications, and sharing settings for meetings in your organization.

Updated yesterday

The Permissions settings page allows you to manage consent preferences, meeting controls, and sharing options for your organization. These configurations ensure compliance with data protection regulations, control over who can access meeting data, and secure information sharing.

1. Consent

Participants will receive a consent email explaining the Privacy Policy and Data Processing Addendum before a meeting.

This email is only sent 30 minutes before scheduled meetings in the calendar. For instant meetings where the bot is manually invited, no email will be sent.

  • GDPR Consent Email

Participants will receive a consent email explaining the Privacy Policy and Data Processing Addendum before a meeting.

  • Recommended for organizations operating in regions under GDPR regulations.

  • Options:

    • Always Send – Consent emails are automatically sent before every meeting.

    • Never Send – No consent email is sent.

  • KVKK Consent Email

Participants will receive a consent email explaining the same privacy details, designed for regions where KVKK (Turkey’s Data Protection Law) applies.

  • Options:

    • Always Send – Consent emails are automatically sent before every meeting.

    • Never Send – No consent email is sent.


  • Recording Notification Message (Zoom Only)

When enabled, Spiky will automatically post a message in the Zoom meeting chat informing participants that the meeting is being recorded and providing privacy information.


  • Real-Time Notification Message

Allows Spiky to post a link in the meeting chat granting participants access to Real-Time Insights.
If turned off, insights remain available through the Meeting Dashboard only.

2. Blocked Email Domains

Prevent Spiky from joining meetings that include participants from specific domains.

Use the Manage Domains button to block or unblock email domains.

3. Sharing

Set privacy and sharing permissions for meeting reports and data visibility.

  • Meeting Privacy

    Control how private meetings behave within your organization.

    • Strict Privacy

      • Meeting visibility is limited strictly to people who are added to the access list.

      • Even admins and managers won’t have access to private meetings unless they are participants or explicitly granted access.

    • Moderate Privacy

      • Admins always have visibility into all private meetings.

      • Other users and managers must be manually added to the access list if they should access a private meeting.

    • Privacy Disabled

      • No meetings can be marked as private.

      • Admins automatically see all company meetings.

      • Managers maintain access to meetings held by their team members.

      How to Mark a Meeting as Private?

      You can make your meetings private directly from the Meetings Dashboard.

      Follow these steps:

      1. Go to the Meetings Dashboard.

      2. On the far right of the meeting row, click the three-dot menu.

      3. Select Set as Private from the dropdown menu.


      Once marked as private, the meeting will only be visible to the people allowed based on the meeting privacy settings.


  • Report Ready (non-Spiky Participants)

Choose whether non-Spiky participants should receive the meeting report once it’s ready.

  • Options:

    • Limited Report: Sends a short summary with the Spiky Score and key action items.

    • Full Report: Shares the complete report, including notes, Spiky Score, and all insights.

    • Do Not Send: Keeps reports internal — no emails sent to non-Spiky participants.


  • Meeting Sharing

The meeting-sharing option enables users to generate public and protected links. If this option is disabled, the team member cannot share the meeting report via URL.


  • Add public report link to emails

By default, Report Ready emails contain a public URL to the meeting report. If this option is disabled, Report Ready emails do not contain the public URL.

Did this answer your question?