Falcon Help Center

FALCON GUIDE

Falcon Rundown 1.3.0

Falcon Rundown 1.3.0 Changelog

Version 1.3.0 introduces Access Groups for reusable workspace permissions while keeping the existing individual permission model fully available.

New Feature: Access Groups

  • Reusable team permissions: Create named access groups such as Editors, Producers or Guests and define one shared role and rundown policy for the group.
  • Individual or group-based access: Each member uses either individual permissions or one access group. Existing members remain on individual permissions until they are explicitly moved to a group.
  • Inherited permissions: Members assigned to a group immediately inherit its role and access to all rundowns or a selected set of folders and rundowns.
  • Group-aware invitations: Assign an access group when inviting a new member, or change the permission source for an existing member.
  • Central updates: Editing a group updates every assigned member. Groups in use are protected from deletion until their members are reassigned.
  • REST API support: REST v1 now supports listing, creating, reading, updating and deleting workspace access groups using opaque agp_... IDs.

See Managing Members for the complete Access Groups guide.

Improvements

  • Cleaner Members window: The modal is wider and uses more compact permission controls so member name, permission source, role, filter and inherited status fit more clearly on one row.
  • Improved Access Group editor: Group creation and editing use a cleaner layout consistent with the existing input styling.
  • Clear permission source: The Members window shows whether access is managed individually or inherited from a named group.
  • Consistent filtered access: When a filtered group member creates a permitted folder or rundown, it is added to the group policy for the other group members.
  • Backward-compatible migration: Existing workspace members keep their current role and filters as direct permissions when Access Groups are introduced.

Fixes and Reliability

  • Fixed an audit-log schema mismatch that could cause a 500 error when creating an access group.
  • Permission resolution now fails closed if an assigned access group is missing or invalid.
  • Workspace, folder, rundown, asset, favourite, schedule and REST operations now use the same effective permission source consistently.
  • Access Group writes use transactions, ownership checks and version-aware updates to reduce conflicting changes.
  • Filtered access is enforced consistently when listing, reading and creating workspace content.

Still need help?

Create a support ticket and tell us what you are trying to do.

Contact support