⌘K

User Roles and Permissions

Falcon Rundown uses a role-based permission system to control what team members can do within a project. When you invite someone to a project, you assign them one of the following roles.

 

Owner

The project owner has full control over the project and can:

 

  • Create, edit, and delete rundowns and stories

  • Invite and remove project members

  • Change member roles and permissions

  • Set up asset packages for the project

  • Transfer project ownership to another member

  • Delete the project

  • Configure project settings

 

Note: Each project has exactly one owner. Ownership can be transferred to another member.

 

Superuser

Superusers have administrative access similar to the owner, with these capabilities:

 

  • Create, edit, and delete rundowns and stories

  • Invite and remove project members

  • Change member roles and permissions

  • Set up asset packages

  • Manage all project content

 

Limitations: Superusers cannot delete the project or transfer ownership.

 

Read/Write

Members with Read/Write access can work with content but cannot manage the team:

 

  • Create, edit, and delete rundowns and stories

  • Add comments to stories and rundowns

  • Use the prompter and cuecard features

  • Print and export rundowns

  • Access project history (if available in plan)

 

Limitations: Cannot manage project members, settings, or asset packages.

 

Read/ Write Comments Only

This role is designed for reviewers and stakeholders who need to provide feedback through the comment system:

  • View all rundowns and stories

  • Add, edit, and delete their own comments

  • View other members’ comments

  • Use read-only features (prompter view, etc.)


Limitations: Cannot edit any content or project structure

 

Read Only

The most restricted role, suitable for observers:

  • View all rundowns and stories

  • Use read-only features (prompter view, etc.)

 

Limitations: Cannot edit content, add comments, or make any changes to the project.

 

Changing Member Roles

Project owners and superusers can change a member’s role at any time:

  • Open the project

  • Click Manage members from the project menu

  • Select the desired role from the dropdown next to the member’s name

 

Best Practices

 

  • Assign Read/Write access to active team members who create content

  • Use Comment Only for reviewers, directors, and stakeholders

  • Reserve Superuser for trusted administrators

  • Use Read Only for observers or clients who only need visibility