What is a distributed publishing model?
A distributed publishing model enables your intranet team to spread the responsibility of publishing intranet content to wider teams whilst still maintaining control.
Usually, this will mean that your organisation enables departments and teams to contribute content to the intranet within their own specific areas.
Implementing a distributed publishing model in Invotra
You can use the site section roles within Invotra to set up your distributed model. Site section roles grant permissions to users within a specific area of the intranet without being able to influence other areas.
The site section roles that are available are as follows:
|Section author||● Create all types of content within sections and sub-sections they are a member of
● Set content to ‘Needs Review’ in their section(s) but not able to publish content
● Edit their own content but not anyone else’s
|Section editor||● All of the above
● Set content to ‘Reviewed’ within their section(s) but not able to publish content
● Edit any content within their section(s)
|Section publisher||● All of the above
● Publish any content within their section(s)
● Delete any content within their section(s)
|Section content reviewer||● Receives emails for all content when it is nearing its review date within their section(s)|
|Section Manager||● Create, edit and delete site sections within their areas
● Use the In Place Editor on site sections within their areas
All of the above roles can be paired with each other to achieve your distributed publishing team. For example, someone can be both a Section Publisher and Section Manager if you want them to manage all content within a specific area of the intranet.
To manage and apply section roles:
1. Navigate to the site section where you want to apply a distributed team
2. Hover over ‘Options’ and click ‘Manage’
3. Use the ‘Add member’ function to add individuals to your site section or use the ‘Team’ tab to add entire teams to a section from the directory
4. Add or remove roles by ticking the user(s) and selecting ‘Choose an action’ where you can: