CloudyFy TV
CloudyFy TVPlatform

Give every teammate exactly the access they need, nothing more

Roles and permissions control what each person in your account can see and change, broken into 34 permission modules that each grant view-only or full management access. Start from a built-in role template, or build your own.

Start free trialSee roles in action

7-day free trial. No commitment.

Settings / Users and rolesSave
OwnerFull access
Content managerPublish and edit
Branch operatorAssigned screens
Read onlyView reports
Now playing

What are roles and permissions in CloudyFy TV?

Roles and permissions decide what a teammate can see and do inside your CloudyFy TV account. Instead of one all-or-nothing login, access is broken into 34 permission modules covering everything from devices and layouts to billing and the restaurant vertical apps, and each module can be granted as view-only, full management, or left out entirely. A role is a named bundle of those grants; assign a role to a user and that bundle becomes their access.

CloudyFy TV ships built-in role templates for common jobs: a Company Admin with full access, a Store Manager who runs devices, publishing, locations, menus and the kitchen integration, a Kitchen Staff role scoped to running the kitchen board, a Marketing role with read-only reporting, and a Content Editor limited to media and layouts. Every template is available on every plan, including Starter. You can also build custom roles from the same 34 modules for anything those don't cover, also on every plan today.

34Permission modules across devices, content, billing and more
5Built-in role templates included on every plan

The 34 permission modules

Permissions are grouped into twelve functional areas below. Every module can be granted as view access, manage access, or both, independently of every other module.

  • Users & roles

    Permission modules
    Users, Roles
  • Company & settings

    Permission modules
    Company profile, Settings, Branding & white label, SSO configuration
  • Devices & fleet

    Permission modules
    Devices, Device groups, Locations
  • Display walls

    Permission modules
    Display walls
  • Content library

    Permission modules
    Layouts, Layout templates, Media library, Media folders, Playlists
  • Scheduling & publishing

    Permission modules
    Schedules, Publish jobs, Releases
  • Engagement apps

    Permission modules
    Popups, Donor walls, Announcements, Donors
  • Reporting

    Permission modules
    Reports, Analytics, Audit logs
  • Alerts & integrations

    Permission modules
    Alerts, Integrations
  • Billing & credits

    Permission modules
    Billing, AI credits
  • Vertical apps

    Permission modules
    Rate boards, Token queues, Live ticker
  • Restaurant

    Permission modules
    Menu boards, Kitchen display

A user can also be narrowed further with a per-user whitelist of specific devices or layouts, so "manage devices" for one person can mean three screens, not the whole fleet.

This granularity is what lets one CloudyFy TV account serve very different jobs without compromise. A single-location retailer might only ever need the built-in templates. A multi-brand reseller managing dozens of customer companies through the partner portal needs to hand different staff different slices of that same 34-module list, sometimes per customer, and the module system is what makes that possible without provisioning separate accounts.

Why does fine-grained permission control matter?

  • New hires get exactly what their job needs

    A kitchen shift worker gets a role that can run the kitchen board without also being able to touch billing or company settings.

  • A reseller's support staff can be scoped tightly

    Grant a partner's team access to the modules they support, and nothing else.

  • Read-only roles are real

    A marketing teammate can get reporting and analytics access without any ability to change a live screen.

  • Reporting doesn't grant editing

    Modules under Reporting are view-only by design, so seeing the numbers never doubles as permission to change what's on screen.

Roles vs. one shared login

Without real roles, teams either share one admin login, so every action is unattributable and every mistake is fleet-wide, or lock non-admins out of the CMS entirely, which means routine content updates queue up behind whoever holds the one password. CloudyFy TV's 34-module system lets you hand out exactly the access a job needs, whether that's a kitchen worker who only bumps orders or a regional manager who only touches their own devices, without a shared password and without an all-or-nothing choice.

A digital screen in an office lobby, part of a fleet where role-based access controls who can change what.

The proof: built-in roles and where they stop

CloudyFy TV's platform-managed role templates are deliberately narrow where it matters. Kitchen Staff can bump, recall, and add walk-in orders on the kitchen board, but cannot issue POS integration keys, pair screens, or change station configuration; that is a separate "administer kitchen integration" grant a Store Manager role carries instead. Splitting "run the board" from "administer the integration" is a real distinction inside the permission system, not a marketing simplification.

FAQs

Give every teammate exactly the access they need

Start the free trial with the built-in role templates, or build your own.