Skip to main content

Create Public Links

Share your meeting notes or recap with anyone, even outside your workspace

Written by Julia
Updated over a month ago

Public links let you share a view-only version of your meeting notes or meeting recap with people who don't have a Fellow account. This is ideal for sharing information with external stakeholders quickly and securely.

You can create a public link for two things: a meeting note or a meeting recap.

Here are the steps for each case:

Public Links to Meeting Notes

1. Open the meeting note or series you want to share, then click the Share button in the top right corner

2. Click "Copy link" and share it with whoever you want.

This is an example of what the note would look like when accessed via a shared public link. Each anonymous user will show up as an animal icon with the rest of the presence indicators.

If the person is not a meeting attendee and/or a guest that has not been explicitly invited to collaborate in Fellow, then they will see a view-only document. As indicated by this message.

Note: If the person is a meeting attendee with collaboration access, then they'll be redirected to an editable version of the note.

Public Links to Meeting Recaps:

1. Open the meeting recap you want to share, then click the Share button in the top right corner

2. Change the access to 'Anyone with the link'.

3. Once you've changed the privacy settings, you'll see a message confirming the visibility update. Then you can send your recap or copy the link, and anyone will be able to see your meeting recap.

This is an example of what the recap would look like when accessed via the shared public link:

Turning Links Off

To turn off the link and to "turn off" the public shared aspect, you can restrict access to your note or recap.

If someone tries to use a public link after it has been turned off, they will see a 404 page like this, with a note that this link might have expired.

Security Settings

Fellow is built with security in mind, giving you full control over how your data is shared.

Admins can manage this feature under Workspace Settings > Security > Sharing & collaboration.

Additionally, the "Locked Video Setting" under "Security" ensures that external viewers must authenticate themselves to access recordings if enabled.

For added protection, you can require public link viewers to log into their Fellow accounts to view recordings and transcripts. Alternatively, you can disable this requirement to ensure external viewers can check the recaps without any extra steps. The 'locked video' feature ensures external viewers authenticate themselves before accessing shared recordings if this setting is enabled.

Managing Access Permissions for External Viewers of Meeting Recordings in Fellow

What Is the Locked Video Setting?

The locked video setting is a security feature designed to enhance the privacy of your meeting recordings. When this setting is enabled, external viewers—those who do not have a Fellow account—are required to create an account or sign in to authenticate their identity before accessing shared recordings. This measure helps prevent unauthorized access to sensitive materials.

Why Does This Setting Exist?

This feature was introduced to bolster user privacy and ensure that only intended recipients have access to a recording. By requiring viewers to authenticate, Fellow minimizes the risk of unauthorized sharing or exposure of the content.

How to Disable the Locked Video Setting

If you'd prefer to allow external users to view videos without needing to authenticate, you can disable the locked video setting in your workspace settings. Follow these steps:

  1. Navigate to your Workspace Settings within Fellow.

  2. Locate the "Require users to authenticate Setting" under "Security" > "Sharing and Collaboration" settings.

  3. Toggle off the setting that requires users to authenticate to view recordings.

Important Notes

  • Disabling this feature may make your recordings accessible to unintended viewers. Consider the sensitivity of the recordings before making changes.

  • Ensure that all stakeholders are aware of the privacy implications when this security measure is turned off.

Did this answer your question?