{"id":61097,"date":"2012-12-07T15:10:11","date_gmt":"2012-12-07T20:10:11","guid":{"rendered":"http:\/\/www.bu.edu\/tech\/?page_id=61097"},"modified":"2013-04-11T13:57:04","modified_gmt":"2013-04-11T17:57:04","slug":"workflow","status":"publish","type":"page","link":"https:\/\/www.bu.edu\/tech\/services\/cccs\/websites\/www\/wordpress\/advanced-workflows\/section-editing\/workflow\/","title":{"rendered":"Overview of the Section Editing Workflow"},"content":{"rendered":"

Each WordPress site can have multiple users. What a user can and cannot do is determined by their Role<\/strong>, which\u00a0comprises a specific set of capabilities<\/em>, each governing whether or not specific actions are allowed through the administrative interface. More powerful roles\u00a0have very few limitations in terms of editing and publishing content and configuring site settings (site title, widgets, custom menus, etc.). Less powerful roles are only allowed to carry out a limited subset of content management operations. While these two basic types of roles are\u00a0adequate\u00a0for many, they are not sufficient for some sites.<\/p>\n

The BU Section Editing plugin works by introducing a new user role \u2014 Section Editor<\/strong> \u2014 intended for users that require limited editing & publishing capabilities.<\/p>\n

\"Default

Default section editor permissions, as viewed on the Page Order screen<\/p><\/div>\n

Section editors can\u2019t do much until they have been given permission to edit content. Rather than granting content editing permissions to users directly, they are instead assigned to a group. These groups (Section Groups<\/strong>) are defined by the set of permissions they hold, and the list of members who are given authority through them. They can also be given a name and description to help represent their function. Using the group model allows for permissions to be shared by many users. Users can belong to multiple section groups, and can be added or removed from a group at any time.<\/p>\n

\"Section

Section Editor with permission to edit \u201cUndergraduate Program\u201d section<\/p><\/div>\n

Once a Section Editor belongs to a group, their editing and publishing capabilities will be determined by their Section Group memberships. Permissions are cumulative, so section editors are allowed to edit any content that is allowed through their combined group memberships.<\/p>\n

What types of content I can grant permissions to?<\/h3>
<\/p>\n

By default, WordPress ships with two main content types \u2014 Posts<\/strong> and Pages<\/strong>. Both of these content types are referred to generically as posts, and each is an example of a specific Post Type<\/strong>. Post Types can be grouped in to one of two categories: hierarchical and flat. Hierarchical post types (like Pages) allow for parent-child relationships, whereas flat post types (like Posts) only permit a single level of content. “Section”\u00a0in BU Section Editing<\/strong> refers to a page that has children \u2014 something that is only possible with hierarchical post types.<\/p>\n

This plugin allows for permissions to be set for each of these post types, and can also support custom post types that may be defined by plugins or themes. For example, the\u00a0BU Profiles plugin<\/a> uses a custom post type called \u201cProfile\u201d to control editing of profile details.<\/p>\n

<\/div>\n<\/div>\n\n

What can a Section Editor do?<\/h3>
<\/p>\n

By default, not much. Without a Section Group granting them permissions, a Section Editor cannot edit any published content<\/strong>. They can edit drafts, but they are not allowed to publish them. They can also add new posts, but they cannot publish them unless they are inside a section that they are allowed to edit<\/em>. For hierarchical post types, such as Pages, Section Editors are not permitted to move published content to a top-level location.<\/p>\n

Their capabilties for the rest of the WordPress administrative interface are limited as well. Section Editors can not:<\/p>\n