Livestorm Roles & Permissions

In this article, we'll break down the various roles and permissions in Livestorm. We'll explore the responsibilities and access levels of roles such as Workspace Owner, Admin, Member, Guest Speaker, and Attendee.

Permissions of Workspace Owners, Admins, Members#

The permissions granted to users depend on the role they have been assigned. For instance, administrators hold extensive workspace permissions, allowing them full control over the workspace settings, enabling them to create and manage events effortlessly. On the other hand, members possess more limited workspace permissions, often restricted to their own user settings and emails/people attributes:

1Admin: This role possesses all access and edit rights in the workspace settings and can create events.

2Member: This role can only edit their own user settings and emails/people attributes, and they have the ability to create events.

Additionally, if the user is also the workspace owner, they will have the option to delete the workspace or other members.

Workspace Permissions#

Session Permissions#

Overview:
Session Roles define what each person can do during a live event.

They help you:

• Keep private sessions secure

• Assign clear responsibilities to your team

• Maintain consistent control across events

Your team gains more clarity and flexibility, while keeping sensitive content protected.

Default roles and access:
Each participant in a session has a predefined role that determines their permissions. By default:

• Event owner and all workspace Admins always join live sessions as Organizers with full permissions, even if assigned a Viewer role.

• Team Members can be assigned the role of: Organizer, Moderator, Speaker, Viewer

• Registrants can be assigned the role of: Speaker or Viewer

• Guest Speakers must be manually added separately

• Everyone else joins as a Viewer, unless a different role is assigned.

You can change these roles at any time from your event settings.

Admins and security:

Admins now have access to all private events if they have the room link, even if they weren’t explicitly added to the event. This is designed for operational flexibility, but it also increases access.

Admins always enter sessions with Organizer-level permissions, regardless of their assigned role.

Assigning roles:

You can define a default role (e.g. Speaker) for all team members in your General Access settings.

This default role applies automatically when:

• Team members register or join independently

• External participants access a public registration page

You can still manually update anyone’s role at any time.

If an event’s access is set to No access, then:

• External participants cannot join the event at all.

• Team Members will only have access if manually added.

When you update the “No access” permissions, those updates automatically apply to everyone inheriting that role.

Roles types:

Here’s how each role works:

Adding members to Sessions:

When you create a new session:

• All existing event members are added automatically with their assigned role.

• In multi-session events, members are added to every session with the same role.

The complete permission matrix:

Best practices:

• Organizer: 1–2 trusted people.

• Moderators: Plan 1 per 50–100 participants.

• Speakers: Only those presenting content.

• Viewers: Everyone else by default.