Blog

Access Should Follow Your Teams, Not Your Employee List

Permissions work best when they mirror how your organization actually operates: as teams, not as a list of names.

Scroll
by Gerd Willschütz· CEO, ColorDigital··4 min read

Permissions work best when they mirror how your organization actually operates: as teams, not as a list of names.

Quick answer

In DMIx, permissions are now assigned to user groups, not to individual users. A user group represents how your teams already work: a design team, a brand, a season, a permission level. Once someone joins a group, they get exactly the access that group defines. Once they leave it, that access is gone. Nobody has to touch objects, collections, or folders one by one.

Nobody works alone

No designer works alone on a collection. No marketing lead reviews a lab dip by themselves. Product development happens in teams: Men's Design, Brand A Editors, the QC group reviewing this season's approvals. That's the actual unit of work in a fashion company, and it has been for as long as fashion companies have existed.

Software doesn't always catch up to that. It's common for access rights to live at the level of the individual: this person can edit this folder, that person can view that collection. It works, until the team behind the work is the thing that actually matters, and the system has no way to see it.

Groups are the unit that scales

A user group in DMIx is simply the digital shape of a team that already exists: a department, a brand, a season, a role, a permission level. You define what the group can see and do once. Everyone who belongs to it inherits that automatically.

A new designer joins Men's Design. Add them to the group, and they have full edit rights across the structure the team works in, immediately.

A colleague moves off the Marketing team. Remove them from Men's Marketing, and their access to that season's assets ends with it, without hunting through folders.

A brand launches a new season. Extend the group's permissions once, and every current and future member is covered.

The result is access management that scales the way teams actually grow and change, not one that requires a manual update for every person, every time.

What this changes day to day

Onboarding takes minutes, not a checklist. Add someone to the right group and they're productive immediately, with exactly the access their role requires.

Offboarding closes every door at once. Remove someone from a group and every permission tied to it goes with them, across every object, collection, and folder.

Structure stays visible. Looking at your groups shows you how your organization actually divides its work, by brand, by season, by discipline, by access level.

Errors get harder to make. There's no folder-by-folder trail to lose track of. The group is the single source of truth for who can do what.

Building groups that fit your company

There's no single correct way to structure user groups. The right shape depends on how your teams actually collaborate. Common starting points: by department (Design, Marketing, QC), by brand, by season, or by permission level (Edit Users, Read Only Users). A group can also start with a single person and grow from there.

The important thing is that your group structure reflects your teams, not the other way around.

How DMIx supports team-based access

  • Permissions are assigned exclusively to user groups, never to individuals directly
  • Access rights update automatically as group membership changes
  • Bulk Edit Users lets administrators update user functions, brand visibility, and external company visibility for multiple users or groups at once
  • Group structures can be organized by department, brand, season, role, or permission level, matching your company's real structure
  • New team members inherit the correct access the moment they're added to a group

Next steps

  • Review your current permission setup and map it to the teams your company already has
  • Visit the Help Section for step-by-step guidance on creating and editing user groups
  • Explore Bulk Edit Users in User Administration to update multiple users or groups at once

Share this article

Share this article

Frequently asked questions

Can a user belong to more than one group?
Yes. A user can be part of several groups at once, for example a department group and a brand-specific group, and receives the combined access those groups define.
What happens if I remove someone from a group?
They automatically lose the access tied to that group across every object, collection, and folder it covers. No manual cleanup required.
Can permissions still be assigned to a single person?
Yes, by creating a group for that one person. It can be extended to more members later as your team grows.
Topics:Permission ManagementUser GroupsTeam Collaboration
Blog

Access Should Follow Your Teams, Not Your Employee List

Permissions work best when they mirror how your organization actually operates: as teams, not as a list of names.