Support · Admin guide

Roles and Permissions — Mediacast CastControl

What Viewer, Operator and Admin can each do in CastControl, how a role reaches us from your Okta or Entra tenant, and what needs no role at all.

For customer it

No group is needed to use a controller. A member of your staff who is assigned the CastControl app in your identity provider and mapped to an office by us can sign in and control that office's TV with no group or role at all. Everything on this page is about the admin portal, where your operations and IT people manage controllers, locations and users. If you only need people to control their own office TVs, you can stop reading here.


1. How a role reaches us

You give a person a role in your own identity provider, and it arrives with their sign-in:

Your IdPWhat you assignRole in CastControl
OktaOkta group MediaCast-AdminAdmin
OktaOkta group MediaCast-OperatorOperator
OktaOkta group MediaCast-ViewerViewer
Microsoft Entra IDApp role with value MediaCast-AdminAdmin
Microsoft Entra IDApp role with value MediaCast-OperatorOperator
Microsoft Entra IDApp role with value MediaCast-ViewerViewer

Names are matched exactly, including the capital C in MediaCast. The setup for each IdP is in the IdP setup section of this site.

Roles are re-read on every sign-in. Adding someone to a group grants the role at their next sign-in; removing them removes it at their next sign-in. There is nothing to change on our side.

Each role includes everything below it: an Operator can do everything a Viewer can, and an Admin can do everything an Operator can.


2. Viewer — see everything, change nothing

A Viewer can open the admin portal and look at:

  • Venues, locations (offices, suites, rooms), zones and groups.
  • Endpoints (the players and displays) and their status.
  • Controllers: the layouts that exist, where they are assigned, and how they render.
  • Installed integrations (for example the Wipro Director adapter) and the integration catalogue.
  • Live operations data: operator events, player profiles, suite lists, current controller sessions.
  • Event types.
  • Suite codes: the list of suites and their scan codes on Admin → Suite codes, with each code's status, and the downloads — a suite's QR image or its printable card, and the venue's whole set of cards as one PDF.

A Viewer cannot change any of it, create or recycle a code, or send commands.

Good for: front-of-house leads, help-desk staff, anyone who needs to answer "what is this TV supposed to be doing?" without the ability to alter it.


3. Operator — run the venue day to day

Operator is more powerful than its name suggests. Treat it as the working role for your venue operations team, not as a junior tier.

Everything a Viewer can, plus:

  • Controllers: create, edit, publish and retire controller layouts; assign them to venues, locations or zones.
  • Suite codes: on Admin → Suite codes, create a code for one room, turn a suite's code off or on, pause or resume its daily change (for a kiosk such as a club), recycle a code immediately, and disconnect the phones using it. Creating codes for every suite at once stays with Admin.
  • Office sign-in: create and remove the email-to-room mappings that let a staff member control their own office TV — and add or remove further rooms for a person who covers more than one (an office and a suite, say). Manage room groups: a named set of rooms in a venue ("Field-level suites") that you assign to people, so one group gives every electrician every suite and a room added to the group reaches all of them. These are CastControl groups, not groups in your identity provider. Import a whole list of people and rooms from a CSV file, with a dry run that shows what would change before anything is written; a row can add a room or, with the action column, take one away. (Setting the name guests see through the import's optional guest_name column stays Admin.) A Viewer can see which rooms a person has, but cannot run an import — not even a dry run, since its report lists every person and room in the file.
  • Sessions: see who is connected to a controller, push a message to a participant, end a session.
  • Endpoints: register and edit players and displays, and send them commands (power, input, channel, volume).
  • Integrations: install an integration, and enable or disable an installed one.
  • Suite data: import suite PINs and maintain per-player profiles for the venue's control system, and set a Wipro suite's room kind (suite, office, kiosk or general) on Admin → Wipro suites — the kind decides which controller layout the room's guests get. Other location fields stay Admin. An account assigned to particular venues sees and changes the Wipro suites of those venues only (this holds for Viewers and Admins too).
  • Operations: acknowledge operator events (alerts raised by the platform).

An Operator cannot change an integration's connection settings (the control-system address and its master credentials), delete venues, locations, zones or groups, change branding, or see the audit log — those are Admin.

Good for: the people who run the building on event day.


4. Admin — set the venue up, and take things down

Everything an Operator can, plus:

  • Suite codes, venue-wide: create codes for every suite in one step (Create codes for all suites). Everything else on that page an Operator can do too.
  • Provisioning: create and revoke the token your identity provider uses to send us your list of people (Admin → Provisioning).
  • Venue structure: create and edit venues, locations, zones and groups; bind and unbind a display to a location; delete venues, locations, zones and groups.
  • Wipro suites: unbind a suite from Wipro control on Admin → Wipro suites. The room stays, with its codes and people, but can no longer be controlled until a PIN import lists the suite again, which reconnects the same room and QR code (see the Administrator Guide §5). Only at venues the account is assigned to, when it is assigned to particular venues.
  • Event types: create, edit and delete them, and set the active event type for a venue.
  • Integration settings: configure an installed integration's connection — the control-system address and its master credentials. (Deliberately Admin only: these credentials reach every suite.)
  • Branding: the logo, favicon and colours your staff and guests see.
  • Monitoring: health, service-level indicators, adapter probe results; create and delete alert rules and alert destinations.
  • Audit log: who did what, when.
  • Tenant settings: your organisation's own settings; delete endpoints.
  • Appliances: the list of CastEdge and MediaCaster appliances installed at your venues is available to Admins through the API. The Appliances page in the portal is a Mediacast-staff page today; ask support if you need the list.

Deleting a location removes the people mapped to it. The email-to-office mappings behind office sign-in belong to their location: if a location is deleted, everyone mapped to it loses controller access at once, with no warning on the mapping itself. Rename or re-bind a location rather than deleting and recreating it.

Good for: the one or two people who own CastControl for your organisation.


5. What only Mediacast can do

Some things are reserved for Mediacast staff and are not available to any customer role, whatever group a person is in:

  • Creating organisations and tenants.
  • Provisioning, licensing and decommissioning CastEdge appliances, revealing their bootstrap credentials, binding them to the network edge, and publishing appliance releases.
  • Defining display types for the platform.

If you need one of these, contact support.


6. Two things worth knowing

  • Roles do not affect controllers or guests. A staff member's office controller works through their office mapping, and a suite guest's QR code works through the code. Neither involves a role. Taking away someone's Admin role does not stop them controlling their own office TV; unassigning them from the app does.
  • Most pages now hide what your role cannot do. Suite codes, Users (people, their rooms and room groups) and Wipro suites show a Viewer the lists and downloads without the buttons that change anything, and say so in a note at the top. Some older pages, such as Layouts and Branding, still show a button that, when pressed, is refused with a "forbidden" message. The refusal is real and enforced by the server; the button is not a sign the action would succeed.
  • Users lists everyone (amended 2026-10-15). The page shows every person your identity provider has assigned to CastControl — before their first sign-in — together with anyone who has a room mapping, their MediaCast-* groups and whether they are active. A Viewer sees the whole list, read-only. An Operator (and above) gives rooms: Give a room on a person who Needs a room, Add every room… (every suite, or another kind of room, in one step), room groups, and removals. The groups shown are what the identity provider pushed; the role in force is still what the person's sign-in token carries.

7. The CastControl groups (amended 2026-10-14)

Two further MediaCast- groups exist alongside Viewer, Operator and Admin. We recognise both at sign-in and keep them on the person's account. Control Admin now grants the Suites view; System Admin still grants nothing extra:

Group / app-role valueRoleTodayPlanned
MediaCast-SystemAdminSystem AdminNothing extra. The controller layout designer is an Operator screen today (Operator and Admin can use it).Build and maintain controller layouts without holding Operator or Admin. No date yet.
MediaCast-ControlAdminControl AdminSuites: a list of the rooms assigned to them on Admin → Users — directly, or through a room group they are in — that have controllable TVs (suites, clubs, offices and the rest), searchable and filtered by kind, and Open on any of them to control it as its guest would. No QR code. Each Open lasts an hour and is recorded in your audit log with the person and the room. It grants nothing in the admin portal. See the administrator guide.A group that follows new suites by itself (today a suite added to the venue later is added to a group with Add every suite again).

Which rooms a Control Admin sees. The rooms assigned to them on Admin → Users: their own rooms plus the rooms of every room group they are in (a room in both counts once) — the same rooms their own controller would get. Give an electrician every suite in one step with Add every room… in their row (choose Suites), or, better, create a room group with every suite and put each electrician in it: a suite added to the group later reaches all of them. A Control Admin with no rooms sees an empty Suites page that says to ask you; opening a room that is not theirs is refused. The person is matched by the e-mail address your identity provider sends; an account without an e-mail address holds no rooms. Room groups are CastControl groups, managed on Admin → Users; they are not groups in your identity provider.

A person's controller (their own sign-in, not Suites) carries at most 128 rooms. Someone whose own rooms and group rooms add up to more than that gets the first 128 by room name in their controller; Admin → Users shows a warning on their row, and Suites still lists every room.

An Admin can use Suites too, from the Suites link in the portal, and sees every room in the venue. A person who is both an Admin and a Control Admin sees every room.

Signing in with more than one. A person who is in MediaCast-ControlAdmin and one of Viewer, Operator or Admin is asked once, after signing in, whether to open Suites or Administration. The device remembers the answer; for that person Suites sits inside the admin navigation, so they switch with Suites or Dashboard there. A person in MediaCast-ControlAdmin only goes straight to Suites, on its own.

Leaving the group. Removing a person from MediaCast-ControlAdmin stops them opening rooms from their next sign-in; a room they already opened stays open until its hour is up. Deactivating them in your identity provider (with user provisioning, §3 of the administrator guide) ends those sessions at once.

`MediaCast-User` is retired (2026-10-08). It never granted anything, and it is no longer read. You can delete the group. Who may sign in is decided by assigning the person the CastControl app in your identity provider; what they control is decided by the rooms mapped to them on Admin → Users. Nothing else is needed for a person to control their own office TV.

8. Choosing groups: a suggested starting point

GroupPut in it
MediaCast-AdminOne or two owners of CastControl in your organisation.
MediaCast-OperatorThe venue operations team that runs event days: they manage people and rooms on Users and run Suite codes day to day.
MediaCast-ViewerHelp desk, front-of-house leads, anyone who needs to look but not touch — including looking up a suite's code and printing its card.
MediaCast-SystemAdminOptional today (grants nothing extra yet). Whoever will build and maintain your controllers.
MediaCast-ControlAdminThe people who service many rooms, such as electricians and suite-control staff. They get Suites: the rooms you assign them on Admin → Users — directly or through a room group — and open any of them as a controller. Put a room group with every suite together once and add each of them to it.
(no group)Everyone who should control their own office TV. Assign them the app, then map their room on Admin → Users (or import a list).