Skip to main content

Permissions

Updated this week

Control exactly what different users can see and do in Fusion Signage – across the whole account and down to specific items. Permissions are available with an Advanced or Pro Licence.

What are permission groups?

A permission group is a reusable set of rules you assign to users. Each group has two layers:

  1. Global permissions – broad 'on / off' capabilities across the entire account (whether members of the group can view, edit, or create screens, media, playlists, and schedules).

  2. Granular permissions – precise access to individual items (specific screens, media folders, playlists, or schedules). Use this to tailor who can see or edit exactly which items.

Handy hint – if you have a Pro Licence, take a look at our locations feature for even more control.

Global permissions

Global permissions set the baseline capabilities for the group across key areas. For each area below, choose the highest level the group should have:

  • View – can see items, but cannot make changes.

  • View and modify – can see and edit existing items.

  • Create – can add new items (like upload media, make playlists, create schedules or screens).

You can set these for:

  • Screens – view, view and modify, create.

  • Screen groups – view, view and modify, create.

  • Media Folders – view, view and modify, create.

    • Approval access

  • Playlists – view, view and modify, create.

  • Schedules – view, view and modify, create.

Please note – if users need to upload media or create playlists / schedules, they must have 'create' at the global level for that area – even if you plan to restrict what they see with granular permissions.

Granular permissions (who sees what)

Granular permissions let you toggle access to specific items so each group sees only what you choose.

  • Screens – pick exactly which screens this group can view or view and modify.

  • Media folders – choose the specific folders this group can access – pair with global 'create' if they need to upload into allowed folders.

  • Playlists – select which playlists they can see or edit.

  • Schedules – restrict access to the schedules that matter to this group.

Here's an example of how you can fine-tune the experience.

  • Turn on the screens that team should manage – leave the rest off.

  • Allow a Retail Team to see Retail > Hero Videos and Retail > Seasonal folders, but not Corporate > Internal.

  • Give Marketing 'View & Modify' access on the National Promo Playlist, while Sales can only view it.

  • Let venue managers modify only their venue’s schedule.

Rule of thumb – use global permissions to set what types of actions are possible (view / edit / create). Use granular to decide the exact items they can touch. If global doesn’t permit an action, granular can’t grant it.

Example setups

Example 1 – store staff (tight scope)

  • Global

    • Media folders = view and modify

    • Playlists = view and modify

    • Schedules = view and modify (no create)

  • Granular

    • Allow Store 17 only media, playlists, and schedules.

    • This means they can update content for their store, but can’t create new folders, playlists, schedules or touch other stores.

Example 2 – Marketing Team (creative control)

  • Global

    • Media folders = create

    • Playlists = create

    • Schedules = view and modify

  • Granular

    • Media folders limited to Campaigns 2025, Brand Library

    • Playlists limited to National Promo and Evergreen.

    • Result = they can upload assets and create playlists but only within approved folders and playlists.

Example 3 – read-only users

  • Global

    • Screens / media / playlists / schedules = view.

  • Granular

    • Select the exact screens and playlists they should see.

    • Result = they can monitor without risk of accidental edits.

Best practices

  • Least privilege first – give only what’s needed to do the job, then add more if required.

  • Name groups clearly – 'Store-Level Editors (QLD)' or 'Marketing – Playlists and Schedules'.

  • Pilot with a test user – confirm visibility matches expectations before rolling out.

  • Review quarterly – as teams and campaigns change, permissions should too.

Did this answer your question?