Users can be added to the team of an initiative and the team of a benefit through the Team sub-menu. Different roles with different rights are possible for Initiatives and Benefits. It is possible to create specific custom roles and configure the rights you need for the role.
To create a new role:
- Click on Team & Roles.
- Click on Create a New Role to display the add form.
- Enter a Name for the role.
- Select a role type from the drop-down list.
- Select Write Access if a user with this role should have permission to create or make changes to objects.
- Select External Access if you want this role to be available to select for an external stakeholder.
- Select neither option if you only want a user with this role to have read access and don't want this role to be available for an external stakeholder.
- Configure your Cascading Permissions.
Cascade Permissions, if set, will ensure that the content of the current entity, will have the same permissions as the parent. If the role with cascade permissions is added to an initiative team, it will have access to all sub-initiatives, benefits, measures and all the rest of the components selected in Specific Permissions box.
Please note that the ability to read or write depends upon whether the Write Access setting is enabled. For example, if a role is created with cascade permissions but no write access and added to an initiative's team, the user will have access to the initiative, sub initiatives, benefits, costs, RAID and all the other selected specific permissions, but it will be read-only access. If the role with cascade permissions and specific permission on Benefit is added to a benefit team, then they will have automatic access to its measures.
If you disable Cascade Permissions, but enable Specific Permissions on different components, the role will have access only to the initiative and its direct benefits, RAID, or other components.
The table below shows how this works for each role type when attached to an initiative or a benefit team:
View initiative Modify initiative View benefit Modify benefit View measure Modify measure Initiative team Role with write access (e.g. Initiative manager) Role with only read access (e.g. Stakeholder) Benefit team Role with write access (e.g. Benefits realisation manager) Role with only read access (e.g. Stakeholder)
- If you want to indicate that these permissions can be customised when adding a Team Member, configure Allow these permissions to be customised.
- Click on Save.
You can edit an existing team role by clicking on the Edit button next to a team role. The edit team role screen will open. You can change the settings here. Click on the Update team member role button to save the changes.
Click on the Delete button in the edit team role screen to delete the selected team role. A team role can only be deleted when it has not been used in the team builder of an initiative or benefit.
Shared Teams are a great way to create a group of members that can be collectively added or removed from a project. As an example, the organisation may have a constantly changing IT team. Rather than adding or removing specific people from a Benefit/Initiative that the IT team is involved in, you may find it easier to assign and adjust an IT Shared Team. In the Shared Team, members can be added or removed from the group, and this will be applied throughout Amplify.
To create a Shared Team:
- Click on Create a new Team
- Enter a Name.
- Enter a Description.
- Enter a Classification.
- Click on Save.
Once the team is created, you may add people to this group by clicking on the + icon.
Use the toggle button to configure this as a global shared team. Otherwise, it will be a local team, having access to a single Initiative.