The editor role includes permissions related to creating content on the platform. Typically, editor role permissions are added in addition to the default user role. Many customers split their editorial responsibilities between a basic editor role and a higher-ranking chief editor role. To find out more about the chief editor role, read Best practice: Chief editor role.
Assign the role to
If you decide to use only one editor role on your platform, this role should be given to the content creators. Editors are responsible for shaping the overall look of the platform, creating new pages, editing homepages, managing reported content, and accessing the non-highly technical aspects of platform administration.
If you choose to have both a higher-ranking editorial role and a basic editor role, the basic editor role should only have a few extra permissions compared to the user role. Major decisions that affect the entire platform should be reserved for the chief editor role.
Create the role
A typical editor role has the below permissions. You can see the definitions for each permission in List of permissions.
General
- "Create and manage global widgets": This permission allows the user to install widgets within the overview of pages or communities. Since all users can see these widgets, the permission should be assigned only to selected people. If you use split editor roles, assign this only to the higher-ranking editorial role.
- "Manage and create public links for files in documents": Everyone outside your platform can use a public download link. Hence, only a minimal group of people should have this permission. If you use split editor roles, assign this only to the higher-ranking editorial role.
- "Manage hero teaser": As the Hero Teaser is the most prominent place to promote topics on a homepage, only selected people should have permission to define its content. If you use split editor roles, assign this only to the higher-ranking editorial role.
- "Manage reported content": Users with this permission will be notified if somebody reports a piece of content.
- "Act in the name of a page, community or event (locally)": This permission allows users to publish timeline and blog posts in the name of the page or community where the app is installed.
- "Act in the name of a page, community, or event (global)": This permission allows users to post blog posts in the name of the page or community where the app is installed and create timeline posts in the name of every page or community they are an admin of in any element on the platform. If you use split editor roles, assign this only to the higher-ranking editorial role.
- "Invite groups": This permission allows users to invite groups to events or communities.
- "Invite communities": This permission allows users to invite all community members to an event.
- "Invite pages": This permission allows users to invite all page subscribers to an event. This effectively means inviting the whole platform for a page that is auto-subscribed to everyone.
- "Switch between homepage sets": If you use homepage sets, this permission allows you to switch between the sets that are visible to you.
- "Analytics admin access": This permission provides full access to the platform analytics. If you use split editor roles, assign this only to the higher-ranking editorial role.
Pages
- "Create page": This permission allows the user to create a new page. Without the permission "Create public page", a user can only create private pages.
- "Create public page": This permission allows users to create new public pages. If you use split editor roles, this permission is often only assigned to the higher-ranking editorial role.
- "Delete page": This permission allows users to delete a page if they are an admin of that page. If you use split editor roles, this permission is often only assigned to the higher-ranking editorial role.
- "Set pages to auto-subscribe": This permission allows users to auto-subscribe selected users or groups or everyone to a page they have created and/or are an admin of. If you use split editor roles, assign this only to the higher-ranking editorial role.
- "Manage categories": This permission allows users to create or edit categories for pages. If you use split editor roles, assign this only to the higher-ranking editorial role.
Communities
- "Manage categories": This permission allows users to create or edit categories for communities. If you use split editor roles, assign this only to the higher-ranking editorial role.
- "Invite externals": This permission allows users to invite externals to a specific community. Externals can only access the specific community they were invited to and cannot see any other parts of the platform. If you use split editor roles, assign this only to the higher-ranking editorial role.
Timeline
- "Create sticky timeline items": Sticky posts are highlighted and stay at the top of the timeline for a defined amount of time. This feature should be used cautiously so as not to dilute the effect. If you use split editor roles, assign this only to the higher-ranking editorial role.
- "Create locked timeline items": Locked posts can't be liked or commented on. The feature should be used with caution, as locked posts run counter to the social character of the platform. If you use split editor roles, assign this only to the higher-ranking editorial role.
Administration
- "Manage users, groups and roles": This permission grants access to the Administration's User management section. Users with access can create and edit new users, groups, or roles. If you use split editor roles, assign this only to the higher-ranking editorial role.
- "Manage features": This permission grants access to the Administration's Features section. Users with access can turn apps and widgets on or off. If you use split editor roles, assign this only to the higher-ranking editorial role.
- "Manage plug-ins": This permission grants access to the Plug-ins section within the Features section of the Administration. Purchased Plug-ins can be enabled here globally. If you use split editor roles, assign this only to the higher-ranking editorial role.
- "Manage themes": This permission grants access to the Administration's Themes section, where users can edit the platform's design. If you use split editor roles, assign this only to the higher-ranking editorial role.
- "Manage languages": This permission grants access to the Administration's Languages section. Users with access can activate and deactivate platform languages and change translations on the platform. If you use split editor roles, assign this only to the higher-ranking editorial role.
- "Manage terms of use": This permission grants access to the Administration's Terms of Use section. Users with access can create, edit, or reset the platform's terms of use. If you use split editor roles, assign this only to the higher-ranking editorial role
- "Access moderator mode": This permission allows users to enter the moderator mode. Caution: The moderator mode should only be assigned to a minimal group of users. If you use split editor roles, assign this only to the higher-ranking editorial role.
- In some scenarios, even a dedicated role makes sense. Learn more in Best practices: Unique roles > Moderators.
- "Manage homepages": This permission grants access to the Administration's Homepages section. Users with access can create new homepages and manage existing ones. If you use split editor roles, assign this only to the higher-ranking editorial role.
- "Manage categories for the launchpad": This permission grants access to the Administration's Launchpad section. Users with access can activate or deactivate the launchpad and create or edit the launchpad's categories. If you use split editor roles, assign this only to the higher-ranking editorial role.
- "Access reports": This permission grants access to the Administration's Reports section. Users with access can see basic platform analytics. If you use split editor roles, assign this only to the higher-ranking editorial role.
Mobile App
- "Send push notifications": This permission allows users to send a push notification to the mobile app of page subscribers or community members when publishing a new blog article.