Content delegation

Introduction

Delegation is the assignment of any responsibility or authority to another person to carry out specific activities. In the digital signage context, content delegation means separating design and copywriting tasks, so that non-IT personnel can input content into an approved design template and management / publisher can approve its publication.

Federate governance in large entreprises

Content delegation

Within a multi-site deployment, the content management might raise some challenges - for instance, a content manager from a company headquarters would create and schedule the global communication, yet most often, the local branches would need to have their own local content included as well.

This kind of situation is addressed through content delegation, a special feature of the HMP350 and HMP300, which allows a content manager to assign the responsibility to manage the content for specific screens to another person. Empowering the subordinate to make decisions in regards to content displayed on a local branch can save money and time, help in building skills, and motivate people.

Implementation

Delegate content creation via web interface.

Content delegation can be implemented by combining local content, managed through the player web interface, with external content, managed through Elementi.

Taking the example above, the two actors would have to do the following:

• The HQ content manager uses Elementi M / X to:
  1. Create / update a project dedicated to global communication of the company.
  2. Publish this project on a content server using the Publish Location feature.
• The local branch content manager uses the player web interface to:
  1. Configure the local branch HMPs to retrieve the "global content" project from the content server using Scheduled Download.
  2. Create content, such as Playouts and Playlists, for local branch communication needs.
  3. Schedule the "global content" as default content and the local content at different time slots. Or vice versa depending on the requirements.

This way, the local branch players would display a mix of globally-distributed content and locally-created content.

Note:

The method above does not enforce any restrictions on how the "global content" is used locally. For alternatives, see how to restrict access to parts of the project.