Screenpublishing offers an extremely granular user permission system. This way, it is possible to allow only specific users to review and publish content to players.
To better illustrate this example, let’s create three roles on the flow:
🧑🎨 Designer – Person in charge of creating layouts and uploading new content to the platform.
🕵️ Editor – Manager in charge of reviewing, approving, and publishing the content created by the Designer.
🧑💻 IT Admin – Person in charge of managing all account permissions.
To support the approval flow, we further recommend creating a folder structure which reflects this process. For this, we create the following folder structure:
\Design – Folder(s) where the design team will create and upload content
\Design\Pending review\Editor\PublishedHow the process works
The Designer uploads assets, structure campaigns, and even playlists to the \Design folder.
Once the Designer’s job is finished and publish-ready, the content should be copied to the folder \Design\Pending review.
The Designer sends an email to the Editor saying the content is ready to be published to a specific player or player group.
Once the Editor gets the email, he reviews the content and either:
Approves for publishing, meaning the content will be published following the required rules. To keep the structure organized, we also recommend moving the published content to the folder \Editor\Published.
Updates, in case any changes need to be made, then approves the content for publishing. Same process as described above.
Rejects, meaning the content will be returned to the Designer for review and updates.