Skip to content
  • There are no suggestions because the search field is empty.

Understanding User Role Types

User Roles determine what each person is allowed to see and do inside the Sardius Media Control Panel. These roles help keep your workspace secure by making sure only the right people can manage content, layouts, and settings. Each role has its own permissions, which can either grant access to features or restrict them.

Owner

The Owner role has full access to every service and action in the Sardius Control Panel. Owners can manage all content, settings, users, and system-level operations.

What makes Owners unique:

  • Only Owners can fully manage Users and Roles

  • Only Owners can create, update, or delete Roles

  • Only Owners can manage all user types, including non-admins

  • Owners have full read/write/delete access to every backend service

In short:
Owners can do everything—no restrictions.
This role is ideal for organizational leadership, primary account holders, and anyone responsible for full system oversight.



Admin

Admins have broad access to almost every service in the SCP but with a few key limits to protect system-wide configuration.

Admins CAN:

  • Manage nearly all content, layouts, assets, bios, categories, and site settings

  • Create and manage Admin users

  • Read/write/delete most services

  • Manage events, calendars, players, analytics, and more

Admins CANNOT:

  • Create or update Roles

  • Manage non-admin users

  • Delete Feeds

  • Access certain backend services such as Polls, Stream, Streams, and Voice


In short:
Admins can run the day-to-day system and manage most settings but cannot control user roles or certain high-level services.
Best for operations managers, media directors, and senior staff.



Editor

The Editor role is more limited but still provides access to all the essential tools needed to manage content.

Editors CAN:

  • Manage Sites (including services inside a site)

  • View and manage Viewers

  • Edit Assets, Bios, Categories

  • Work with Polls and Player Stats

  • Read/write/delete many content-related services

Editors CANNOT:

  • Access or modify system-level settings

  • Manage Payments, Feeds, Locations, Places, Products

  • Upload files (Files service is restricted)

  • Work with advanced or sensitive backend services

  • Access Streams, SCP core configuration, Voice, etc.


In short:
Editors manage content but have no access to system settings.
This role is ideal for content teams, uploaders, and staff who prepare weekly or regular media without needing access to global controls.



Custom Roles

If your team has unique responsibilities, you can create Custom Roles tailored to the exact access each person needs. Custom Roles allow you to design a permission set that matches the specific responsibilities of your staff, volunteers, or moderators.

When creating a custom role, think about which features the role should access and what level of permission is appropriate.

You can assign one of three permission types to each feature set:

  • No Access
    The user will not see or access the feature at all.

  • Full Access
    Grants the user complete control of that feature set (similar to an admin).

  • Custom
    Allows you to fine-tune access based on what the user should be able to do.
    (Available for some tools and services.)

In short:
Custom Roles let you build the exact permissions your team needs — nothing more, nothing less.


Summary Comparison

Role Best For Access Level Key Limitations Customizable?
Owner Primary account holders Full access to all services and users None No (already full access)
Admin Managers, directors Broad system access Cannot manage roles, some services restricted No
Editor Content teams Content-focused access No system settings, limited service access No
Custom Role Specialized team roles, volunteers, moderators You choose (No Access, Full Access, or Custom per feature) Depends on how the role is configured Yes (fully customizable)