August 3, 2022 | 3 Min

Coming Soon: Self-Service User Management

Neil Cooper
AuthorNeil Cooper
Default hero
AnnouncementProduct updatesEngineering
Over the coming months we will be releasing a number of features to allow Amplience customers to manage their own access within the platform. The first of those releases is Organizations.

What Are Organizations?

Simply put, Organizations are a container. A top level entity that will allow you to organize your users, hubs and repositories.

For Dynamic Content this will mean that you can see the hubs and repositories that belong to your Organization. It will also mean you can invite and remove users from your Organization and manage which users are administrators of your Organization.

What Difference Do Organizations Make?

Organizations will allow administrators to see all the users that belong to their account. As we release more features over the coming months it will become a powerful tool to control access to resources.

Within the new account app, admins will be able to manage which users have which roles, on which resources. This allows you granular control over what your users can do; e.g. Only allow certain users to manage slots, and therefore add protection from erroneous content deployments. Or, only grant visibility to certain repositories, removing the sometimes overwhelming volume of content that is visible to content creators.

Another benefit of Organizations is its combination with the recently released Asset Tab in Dynamic Content. As many Dynamic Content users no longer need a matching Content Hub account to upload assets we can now remove the need for alias accounts, or impersonation for those users. A single account can now upload assets using the Asset tab.

Roles to Group Together Common User Permissions

One of the next elements of Self Service User Management will be Roles. Roles group together sets of actions that are common for a user to need to be able to perform. We’ve created a solution that allows a user to have a role per hub/repository.

A user will have a role for an Organization, which could be different to the role they have on a Hub and on a Repository. This gives admins the control over who can do what within their business, but also a high degree of configurability.

Organizations has two roles; Admin and Member. Member is the default role assigned to all users that accept an invite into an Organization. Admin is the role that is able to assign roles to other users, it’s likely that this admin role will be extended in future for other Organization level actions.

Hubs & Repositories have 5 roles: Admin, Developer, Publisher and Author for both. As well as Member for Hubs and Viewer for Repositories.

For our existing customers these map closely to the Personas used for provisioning users.

Other Features in the Works


Teams will give admins the ability to group users together and assign roles to the entire team, rather than having to assign them one user at a time.

This will mirror the way users work in the platform - with multiple users working together in the same Hubs and Repositories to build and publish content

User Creation

Putting User creation in the hands of our customers is vitally important to the goal of the self-serve project as it removes one of the key barriers for customers to manage users without ever needing to raise a support ticket.

We Want to Hear From You!

If you are an existing customer, get in touch with your Customer Success Manager to give you more detail on Self Service User Management.