Groups (beta) – Sharing access to media with Group-Based Access

Last Updated 8 days ago

Groups let you give selected users access to media in selected Categories – without raising their Role to give them access to the whole media library.

Users with the Role “User” or “Producer” normally see and manage only their own media. With Groups, an Administrator can let those users view or manage media owned by others, but only in the Categories the Group has been given access to. Roles with broader permissions (Publisher and Administrator) already have account-wide access and are not affected.

Read this first:
Categories are open to everyone by default. As soon as you give any Group access to a Category, that Category becomes restricted for Users and Producers and only Groups that have been given access to it (and Administrators and Publishers) can work with it. Read the full article before assigning groups to categories.

Before you start

Who can set up Groups: Only Adminstrators

Who benefits: users with the Role “User” or “Producer”. Publishers and Administrators already have access to all media.

Availability: Available to everyone.

Plan your Categories first. Groups give access per Category, so you need a Category structure that matches how your teams work (for example one per department or project).

Why use Groups?

By default, access to media is decided by the user’s Role and by who owns the media. Groups add a second layer so you can share media for a specific team or project without changing anyone’s Role. Typical uses:

Collaborate within a team – give several users access to the same Categories without opening the whole library.

Separate departments – let each team work with its own content without seeing unrelated media.

Give view-only access – let users view media owned by others without being able to change it.

Share responsibility for media – give a team "Manage media" access when several people need to maintain the same content.

Build structured access with hierarchical Categories – organise content by department, team or project, and grant access only where needed.

Key concepts

Term

What it means

Role

The user’s baseline permissions (User, Producer, Publisher, Administrator). Groups never reduce what a Role already allows.

Media ownership

The user who uploaded or owns a media item. Groups do not change who owns a media item – they only extend access for other users.

Category

A folder-like label used to organize media. Categories are also the boundary for Group access: access is set per Category.

Group

A named set of users. A Group is given an access level for each Category it should reach. A user can be a member of more than one Group.

Access level

What a Group may do in a Category: Own media, View media or Manage media (see “Access levels”).

Quick start: give a team access to a Category

This example gives the Marketing team view-only access to the Category “Campaigns”.

  1. Go to Settings → Users → Groups and create a Group, for example “Marketing”.
  2. Add the team’s members to the Group. Only users with the Role “User” or “Producer” gain anything from membership.
  3. Repeat steps 1–2 for every other Group that needs to keep working in “Campaigns”.
  4. Open Settings → Metadata → Categories and open the Category “Campaigns”.
  5. Choose the Group “Marketing” and set the access level to Manage media.
  6. Save. “Campaigns” is now restricted: only the Groups you added can work with it.
  7. Check the result: sign in as (or ask) a Marketing member and confirm they can see media in “Campaigns” but cannot add or edit
image

You can configure the same access from either place: on the Group (Settings → Users → Groups) or on the Category (Settings → Metadata → Categories). Both change the same setting

image

Access levels

Access is set per Category, so the same Group can have different levels in different Categories. Choose one level for each Group and Category:

Level

See the Category

See others’ media

Add media

Edit / delete media

Notes

No restrictions

Yes (everyone)

No – own media only

Yes

Own media only

No Group has been assigned. Applies to every user.

Own media

Only if they own media in it or have access to a subcategory

No – own media only

No

Own media only

Owned media can still be deleted.

View media

Yes

Yes

No

No

Read-only access to all media in the Category.

Manage media

Yes

Yes

Yes

Yes

All rights to media as the owner of the media.

Choosing a level: use View media for people who only need to watch, publish, use or review, Manage media for people who share responsibility for the content. Own media is automatic for users to keep working only with their own media in a Category that is otherwise restricted.

How Group-Based Access works

A user’s Role gives their baseline permissions. Group-Based Access is an extra layer on top, applied Category by Category.

  • Groups add access; they never take away what a Role already gives. Publishers and Administrators keep full access.
  • Restricting a Category is what limits other users. Once a Group is given access to a Category, users who are not in a Group with access (and who do not own media there) no longer see that Category.
  • Ownership does not change. A Group only extends access to media owned by other users.

Example

Two users with the Role “User” each own one video in the Category “Projects”: User 1 owns video1 and User 2 owns video2. User 1 is a member of Group A. Group A is then given Manage media access to “Projects”.

-User 1 (member of Group A)User 2 (not in Group A)

Before Group A is given access

Sees the Category “Projects” and their own video1.

Sees the Category “Projects” and their own video2.

After Group A is given Manage access

Sees the Category “Projects”, video1 (as owner) and video2 (through Group A). Can manage both.

Can no longer write to category “Projects”. Still sees and owns video2.

To keep User 2 working in “Projects”, add User 2 to Group A or to another Group that has access to the Category.

Groups and hierarchical Categories

Group-Based Access works with parent and child Categories, and each Category has its own access setting. A user can have access to a child Category without having access to its parent.

Example structure:

  • Company
    • Marketing
      • Campaigns
      • Events

Group A has Manage access to “Campaigns” only. For a member of Group A:

  • “Campaigns” is fully available – they can view, add and manage media there.
  • “Company” and “Marketing” are shown in the category tree as restricted, so that “Campaigns” can be reached. The user cannot place media in them.
  • “Events” is not available
image

A user can see a Category if any of the following is true:

  • their Role gives them access (Administrator or Publisher);
  • one of their Groups gives them access;
  • they own media in the Category;
  • it is the parent of another Category they can access (shown as restricted); or
  • no Group access has been set on it (Unrestricted).

Group access is reflected wherever users browse, filter or assign Categories.

Groups and Single Sign-On (SSO)

If Single Sign-On is enabled on your account, group membership for SSO users is controlled by your identity provider (the SSO federation), not by Quickchannel. Quickchannel Groups still decide what those users can access – only the way users are added to Groups is different.

How it works

  • Groups are matched by name. If a Group in Quickchannel has exactly the same name as a group in your SSO federation, users who have that group in the federation are automatically added to the Quickchannel Group when they sign in. They then get the Group’s access to Categories.
  • Quickchannel learns about SSO groups at sign-in. An SSO group is created in Quickchannel when a user who belongs to it signs in. Before that, the group is not visible in Quickchannel. Administrators can also create the matching Group in advance, which is recommended for new accounts, but it is not required.
  • SSO users cannot be added to Groups manually. Apart from the automatic assignment above, SSO users cannot be added to Quickchannel Groups. They only inherit the groups they have in the federation, and only if a Group with the same name exists in Quickchannel. This means SSO settings cannot be bypassed by assigning users to Groups manually.
  • Editing a group does not show SSO users as members. Quickchannel only knows SSO users who have signed in, so a Group’s member list does not list its SSO users as unseen SSO users may have access to the group. This differs from Groups for non-SSO users, where all members are known and listed

Set up Groups for SSO users

  1. Ask your SSO administrator which groups the federation sends for your users and the exact group names.
  2. In Quickchannel, go to Settings → Users → Groups and create a Group with exactly the same name for each SSO group you want to use. Names are case-sensitive, so “Marketing” and “marketing” are different groups. You can do this before any users have signed in (recommended for new accounts), but it is not required.
  3. Give the Group access to the relevant Categories, following “Quick start” above and the recommended order in the warning at the top.
  4. Ask users to sign in. Their Group membership is refreshed every time they sign in, so a user who is removed from a group in the federation loses that Group’s access at their next sign-in

Keep names identical

Mapping depends entirely on the Group name. If a Group is renamed in either Quickchannel or the SSO federation, the names no longer match and users stop receiving that Group’s access. Rename both sides together, and keep the capitalisation identical.

image

Good to know

  • Several Groups: a user can belong to more than one Group. If two Groups give different levels in the same Category, the higher level applies.
  • Removing a member or deleting a Group: the user loses the access that came from that Group. Media they own stays theirs.
  • Existing media: when a Category becomes restricted, its media keeps its owner; access for others is decided by the Groups.
  • Limits: A user can be a member of at most 20 groups. A category can have a maximum of 20 groups assigned.

Troubleshooting

Problem

What to check

A user cannot see a Category

The Category is probably restricted. Check that the user is a member of a Group that has been given access to it.

A user can see media but cannot upload or edit

The Group likely has View media. Change it to Manage media for that Category.

A whole team lost access to a Category

Another Group was given access first, which restricted the Category. Add the team’s Group to the Category.

A user still sees a Category they should not have access to

They may own media in it, have a Role with broader access (Adminstrator or Publisher), or the Category is the parent of one they can access (shown as restricted).

Changes do not appear for a user

Has the there been a recent configuration change? Try reloading the page.

Related articles

Users page – Managing users, roles and groups

Metadata page – Managing categories, tags and properties

Hierarchical categories

SSO related articles

Loading ...