Access, users and teams

When accessing MK.IO, users are assigned specific permissions that allow them to securely collaborate and use resources within their organization according to their roles and responsibilities.

Concepts

  • Role-based access control (RBAC) is an authorization system that defines permissions based on roles. MK.IO role-based access control helps you manage who has access to MK.IO resources, what they can do with those resources, and what areas they have access to.
  • Organization: a company/group that uses MK.IO.
  • Project: linked to organization and linked to a cloud subscription for billing. Projects hold resources such as assets, live events and transforms.
  • User: physical human. A user may have access to multiple organizations.
  • Team: a group of users within an organization. A team is granted permissions on projects and resources.
Relationship between Organization, Team, User and Project

Relationship between Organization, Team, User and Project

MK.IO comes with an integrated role-based system designed to be straightforward, allowing for a seamless onboarding of new collaborators. The first user in the organization is automatically granted Organization Admin access permissions. The Organization Admin has full control over the system, including the ability to invite users and create an Administrators team that will be able to manage various teams (see table below for permissions).

Manage teams

Being part of an organization means that you're a member of one or more teams. Project access is granted to users through Teams.

By default, every organization has 2 predefined teams: Administrators and Everyone. However, you can create new ones if you have more advanced needs.

  • The Administrators team can only be edited by the Organization admin. Members of the Administrators team have full access and administrative rights to all projects. They may also have some organization-level permissions, such as the ability to view billing information, if permitted (see table below).
  • The Everyone team can be edited by the Organization admin and the members of the Administrators team. This team automatically includes all users of the organization. By default, the Everyone team has access to all projects, with a permission level set by Administrators: either User or Reader. Optionally, the Everyone team can be configured to have no access to all projects.
Permissions

Permissions

Create a team

☝️

This action is only available for the Organization admin and the Administrators if permitted.

  1. From the profile drop-down menu, in the top right corner, navigate to Organization Settings then select Access Management. From the Teams tab, for each existing team, you can view the associated number of members and the number of projects.
  2. If you have the permission, click Create Team, then enter a name and a description.
  3. Once created, you can add users and projects.

Edit the team members

☝️

This action is only available for the Organization admin and the Administrators if permitted.

From the Teams tab, click the 3 vertical dots next to each user. You can either set a user as a Team admin or remove it from the team.

Edit the team details or delete the team

☝️

This action is only available for the Organization admin.

From the Teams tab, click the 3 vertical dots in the top right corner then select the appropriate action.