Identities
Users sign in with an OAuth 2.0 token, for example from your Microsoft Entra ID. Groups reflect your organization, and every identity has one global role: Admin, Editor or Readonly.
PERMISSIONS
The permission model of Agravity GlobalDAM is built on your sign-in, for example through Microsoft Entra ID. One global role, access to content and Feature Profiles for functions: this keeps you in control of content and functions.
AT A GLANCE
Permissions in Agravity GlobalDAM answer three questions: Who are the users, which content may they access, and which functions may they use? Each question has its own layer. Together they determine what a user can see and do.
Users sign in with an OAuth 2.0 token, for example from your Microsoft Entra ID. Groups reflect your organization, and every identity has one global role: Admin, Editor or Readonly.
Workspaces, collection types, download formats and asset relation types define what a group can see and edit.
Feature Profiles determine which of the more than 40 functions a user may use. Default profiles are prepared, and you add custom profiles as needed.
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. 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.
You then grant the groups themselves permissions in Agravity GlobalDAM on the individual elements, for example on workspaces and collection types. You assign permissions preferably to groups, and in exceptional cases to individual users or API keys. Administrators define in the settings which identities are available for this.
Admin, Editor or Readonly: the global role defines how far an identity may act in general. Admins manage settings and permissions, editors maintain content, and Readonly users see and use what has been released for them.
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 way, marketing, sales and agencies each see what is meant for them.
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.
Facets, global filters and status and availability values control what appears in search. Content that is blocked, for example, can be hidden from users with the Readonly role. A global filter can apply to Readonly users only.
Portals give partners or agencies permanent read access to selected content. For sharing individual media, Shares are available in addition. We describe both under Sharing and portals.
With impersonation, administrators see the interface from a user's point of view and can verify that permissions work as planned.
GOOD TO KNOW
A few answers up front.
We'll cover the rest in person.
LET'S TALK
Show us your requirements. We'll show you how Agravity fits.