In this release:
Editor role in Cost Object Permissions*
*Requires Simplified Approvals to be enabled (Learn more)
Based on customer feedback to Simplified Approvals, we've added an Editor role to support a workflow where a user can edit several Cost Objects within a group but have no approval authority. Users can be assigned as an Editor to any level in the Cost Object hierarchy. Editors will be able to edit and submit all child Cost Objects, but will have no authority to approve those plans (Learn more).
In the hierarchy view of the Cost Object Permissions table there are now three columns to assign Owner(s), Editor(s) and View Only users. Select the edit icon to assign a user to one of these roles at any level in the Cost Object hierarchy. From the list view, you can assign a user one of the following Edit Levels: Owner, Edit & Submit (Editor) or View Only (Learn more).
| Edit Level | Assigned to Leaf Cost Object | Assigned to Group Cost Object |
|---|
| Owner | Edit and submit the Leaf Cost Object | Edit and submit the Group Cost Object Edit and submit all children Cost Objects Approve all child Cost Objects |
| Edit & Submit | Edit and submit the Leaf Cost Object | Edit the Group Cost Object Edit and submit all children Cost Objects |
| View Only | Read-only access to the Leaf Cost Object | Read-only access to the Group Cost Object Read-only access to all children Cost Objects |
Edit or import line items at a Group Cost Object level
Budget Process Owners or users assigned as an Owner or Editor to a Group Cost Object can edit or import line items to those Group Cost Objects rather than editing the child Cost Objects individually. Note that Budget Process Owners can edit or import line items including External Line Items for All Cost Objects in an Open plan.
A user with edit permissions can navigate to a Group Cost Object and select the Edit button to enable group editing. Editing a Group Cost Object will edit the latest in-progress version of the child Cost Object. If no in-progress version is available, a new version will be created. Selecting Submit Changes when in group edit mode will submit all in-progress versions within that group.
In the example below, Group A has three child departments: Department 1, Department 2 and Department 3. Department 1 has not started so Version 1 is the latest version, Department 2 has Version 2 in progress and Department 3 has Version 2 in the returned state. Editing Group A would create a new editable version for Department 1 and Department 3 and continue to edit the in-progress version for Department 2.
For information on our release and maintenance schedule, refer to IT Planning Release & Maintenance Schedule