Why permissions in a DAM are more than a rights system

A DAM is rarely an internal tool for a handful of people. Marketing maintains campaign material, sales looks for product images, agencies deliver assets, and partners need approved media. Each of these groups should be able to see and do exactly what is meant for them: no more and no less.

To make this work without constant administrative effort, Agravity GlobalDAM separates three questions. Who is the user? Which content may they access? Which functions may they use? Each question has its own layer, and together they determine what a user can see and do. You will also find a compact overview on our page about the permission model.

Layer 1: Who is the user? Sign-in and identities

Agravity GlobalDAM generally requires an OAuth 2.0 token. This token does not have to come from Microsoft Entra ID or Microsoft Entra External ID. With Entra ID, Agravity GlobalDAM offers a direct integration: single sign-on is therefore included, and your organization's sign-in rules also apply to Agravity GlobalDAM. Identity management stays where you already maintain it. For organizations without their own Entra ID tenant, we often offer Entra External ID. Connecting to your own Entra ID tenant is part of the Standard and Enterprise license plans, see License plans for details.

You then grant the groups themselves permissions in Agravity GlobalDAM on the individual elements. You assign permissions preferably to groups, and in exceptional cases individual users or API keys are possible as well. Administrators define in the settings which identities are available for this.

Every identity gets a global role: Admin, Editor or Readonly. The role defines in general how far someone may act. Admins manage settings and permissions, editors maintain content, and Readonly users see and use what has been released for them.

Layer 2: Which content? Workspaces, collection types and formats

The role does not yet say which content someone can reach. You control that through the structure. For each workspace you decide whether a group can see it or not. For each collection type you assign viewer or editor rights. Download formats and asset relation types can also be released per group.

This has a practical advantage: if you build the structure sensibly, for example with one workspace per brand, region or department, you control access with a few settings. You will find more on the structure under Media management.

Layer 3: Which functions? Feature Profiles

Not everyone who may edit content should use every function. Feature Profiles bundle the functions a user may use. Default profiles exist for Admin, Editor and Viewer, and you can create your own. More than 40 functions are available.

This way, an agency can, for example, upload and tag media without having all functions of the platform at its disposal.

Permissions in search: what someone may not see, they will not find

Permissions also take effect in search. Facets, global filters and status and availability values control what appears in the results. Content that is blocked, for example, can be hidden from users with the Readonly role. A global filter can also apply to Readonly users only. Readonly users therefore see only what is meant for them.

How search itself works is described under AI & search.

An example: marketing, sales, agency and partners

Imagine a company with two brands. One possible setup looks like this:

  • Marketing: Editor role, access to the workspaces of both brands, default profile for editors.
  • Sales: Readonly role, access to the workspaces with product images and sales documents, only released content visible.
  • Agency: Editor role, access only to the workspace of one campaign, a custom Feature Profile with a reduced set of functions.
  • External partners: access through a portal with permanent read access to selected content.

You can share individual media in a targeted way with Shares, see Sharing & portals for more. The example is not a mandatory model. Which setup fits your company depends on your organization and your processes.

Check permissions before it matters

A permission model is only good if you can verify it. With impersonation, administrators see the interface from a user's point of view and can check that permissions work as planned, for example before a new team starts.

Do you have specific requirements, for example from a security questionnaire or an IT review? Then we will work with your IT to clarify how your groups and processes can be mapped. You will find more information on the pages about security & operations and the permission model.