An approval chain is a series of users or user groups who must approve content before it can be published to your website.
An approval chain lets you control how and when your website is updated. For example, if your Web master needs to approve every new content item or update of an existing item, the Web master would be last member of every approval chain and exert total control over the site.
Alternatively, you could set up a less centralized organization, where each department head controls a section. To accommodate this, set up an approval chain for each department, and assign the department head as the last member of the chain. When the last person in the chain approves content, it goes live. Also, if a user deletes content, before it is removed from Ektron, it must pass through the approval chain.
On the opposite extreme, you can delete the approval chain for a content item or folder. In this case, every item in that folder is published as soon as a user submits it for publication.
You can approve, edit, or decline content submitted to you or your user group. The following chart illustrates the approval process.
NOTE: An approver can edit the content and publish it, unless Force All Approvers is set, in which case an edit by any approver would cause the approval chain to start over.
You can create approval chains for a folder and content within a folder. If a content approval chain exists, it overrides the folder approval chain.
You can also set up an approval chain for a language. If you initialize new foreign language content with content from another language, the new content initially has no workflow. You must add it as you would any other workflow. See also: Translating content manually.
An approval chain can include any number of users or user groups.
NOTE: Only members of the administrators group and users assigned to the Folder User Admin Role screen can modify the approval chain. See also: Defining roles
Ektron can automatically send email notification, informing users that content work flow events have either taken place or are requested of them. For example:
The list of automatic emails and directions for customizing their content are described in Customizing Ektron email with tokens.
Finally, the Approval Method determines if content must be approved by all users in the chain, or only users higher up the chain than the one making the edits. See Setting the approval method.
Prerequisite
Only administrators group members and users assigned to the Folder User Admin Role screen can modify the approval chain See also: Defining roles
Before you can create or edit an approval chain, you must access the View screen.
The screen shows the following information about the approval chain.
Best Practice
Assign user groups (and not individual users) to an approval chain. In this way, if someone is out of the office, any group member can approve the content.
NOTE: Only users and user groups with permissions to the folder appear. See Adding a user or user group to the permissions screen for more information.
After you assign approvers to a folder, you may want to adjust the approval order. Place the user or group with final approval authority at the end of the approval chain (that is, the highest number). For example, if you have a content contributor whose edits must be approved by a department head, and the Webmaster has final review of all content, the approval order would look like this:
To edit the approval order:
WARNING! If a user is deleted from a folder's Permissions screen, the user is automatically deleted from the folder's approval chain.
You can change the approval chain for a specific content item. Use the View Content screen's Manage Approvals button to do this.
- You must disable the inheritance of permissions for the content whose approval chain you want to edit. See Setting permissions for content.
- You must assign users or groups to the approval chain. Only users and user groups with permissions to the content may be assigned. See Managing folder and content permissions.
If the approval chain is inherited, you must break inheritance.
NOTE: An approver can edit the content and publish it, unless Force All Approvers is set, in which case an edit by any approver would cause the approval chain to start over.
The following example follows a typical content block from creation to publication. Three users make up this approval chain.
Each user has different permissions that correspond to their roles.
The approval chain begins when a content contributor submits a new or edited content. If email is enabled, an email is sent to the next approver in the approval chain.
After the Sports Writer submits the content, the first user in the approval chain, Sports Editor, receives an email stating content needs approval. Sports Writer can change and approve the content or decline it.
Sports Editor logs into Ektron, goes to the desktop, and sees the Content Awaiting Approval panel.
Sports Editor clicks the View All link and sees all content awaiting approval. The approvals folder window displays information such as title, who submitted it, go live date, and so on. Sports Editor clicks the submitted content.
The View Content Awaiting Approvals window appears listing all information necessary to decide whether to approve or decline the content. At the approval window, the Sports Editor has these options.
NOTE: An approver can edit the content and publish it, unless Force All Approvers is set, in which case an edit by any approver would cause the approval chain to start over.
For this example, choose Publish.
After the content is approved, the next approver in the approval chain receives an email saying that the content is ready for approval.
EditorInChief logs in to Ektron and accesses the Workarea. The Workarea has an Approval folder with the content awaiting approval. EditorInChief gos through the Approval folder to the content Red Sox win World Series.
From this window, EditorInChief can view information about the content, including title, go live date, user who created it, and so on. EditorinChief then clicks the content to be approved.
This window is similar to the previous approver’s but includes a Publish button at the top of the screen. The EditorInChief has a Publish button (instead of a Submit button) because this user is the last approver in the approval chain. When the EditorInChief approves the content, it is published to the website.
Like the Sports Editor, the EditorInChief has the following options:
NOTE: An approver can edit the content and publish it, unless Force All Approvers is set, in which case an edit by any approver would cause the approval chain to start over.
After reviewing the content, the EditorInChief decides it is great and publishes it. At this point, the content becomes live on the website, and the approval chain is complete. The user who created the content receives an email notification that it was published.
The Approval Method determines if content must be approved by all users in the chain, or only users higher up in the chain than the user creating or editing the content. The approval method affects the approval process only if the person submitting or editing content is a member of the approval chain.
Two approval methods are available.
The Approval Method applies to all content in a folder, regardless of its language.
For example, assume the approval method is set as follows:
If the Approval Method is Force All Approvers, and the Department Head submits content, the content must be approved by the content contributor, then the department head, then the Webmaster before it is published.
If the Approval Method is Do Not Force All Approvers, and the Department Head submits content, the content must only be approved the Webmaster before it is published.
Prerequisite
If the approval chain is inherited, you must break inheritance.
By default, the approval method is set to Do Not Force All Approvers. To change the approval method for a content folder or item: