Users & Teams
Castmill provides fine-grained access control through users, roles, and teams.
Users
Roles
Every user within an organization has a role:
| Role | Description |
|---|---|
| Admin | Full control over the organization: manage members, settings, and all resources |
| Member | Create and manage content and devices within allowed teams |
| Viewer | Read-only access to the organization's resources |
Admins can invite new users, change roles, and remove members from the organization.
Inviting Users
To invite a user to your organization:
- Navigate to Organization in the sidebar
- Open the Invitations tab
- Click Invite User
- Enter their email address and select a role
- Send the invitation
The invited user receives an email with a link to join. If they don't have a Castmill account yet, they'll create one during the signup process.
Blocking Users
Network administrators can block users at the network level, preventing them from logging in. Organization admins can remove users from their specific organization.
Teams
Teams are groups of users within an organization. They serve two purposes:
- Collaboration — Group users who work together
- Access control — Restrict which resources (media, playlists, devices, etc.) a user can see and manage
How Team-Based Permissions Work
Resources (media, playlists, channels, devices, layouts) can be assigned to teams. When a resource is assigned to a team:
- Only team members and organization admins can access it
- Resources without a team assignment are visible to all organization members
This enables scenarios like:
- A "Lobby Displays" team manages only lobby-related content and devices
- A "Marketing" team manages only marketing playlists
- Organization admins can see and manage everything regardless of team assignments
Creating a Team
- Navigate to Teams in the sidebar
- Click Add Team
- Enter a name for the team
- Add members to the team
Assigning Resources to Teams
Most resource creation forms include an optional Team field. You can also filter resources by team in any list view using the team filter dropdown.
Permissions Matrix
The permission system checks capabilities at multiple levels:
graph TD
A[User Action] --> B{User Role?}
B -->|Admin| C[✅ Allow]
B -->|Member/Viewer| D{Resource has Team?}
D -->|No Team| E{Has Permission?}
D -->|Has Team| F{User in Team?}
F -->|Yes| E
F -->|No| G[❌ Deny]
E -->|Yes| C
E -->|No| G
Available permissions per resource type:
| Permission | Description |
|---|---|
| Create | Create new instances of a resource |
| Read | View resource details |
| Update | Modify existing resources |
| Delete | Remove resources |
| List | See resources in list views |