Onboard your team

Once you have configured your Fusion Manage Extension site and are happy with the set up, you'll need to start inviting your team. It is important that your team completes some onboarding so that they are familiar with what they will be using the Fusion Manage Extension for on a day-to-day basis.

Manage training data

There are a series of tutorials that you and your team should work through to familiarize yourselves with the full use of Fusion Manage Extension. These tutorials will have your team generate their own data to work with. This may start to clutter your hub and Fusion Manage Extension workspaces over time.

Recommendations

• In order to prevent clutter in your hub, consider creating a project where all training can take place. Each member of your team will work through their tutorials and create similar data to each other, so ensure that each of them creates their own folder in which they can work.
• Consider setting the project permissions to Reader but give each person their own folder with Editor permissions. That way, they can only work with the data they create.
• Consider archiving data on the Fusion Manage Extension side to hide unnecessary data.

Manage change approval templates

As your team are completing the tutorials to release items, they will need to choose a change template. The change template is mandatory and specifies change coordinators who can progress change request and change order workflows, as well as approvers to sign off on changes. There are several ways you might approach how you manage change templates and tutorial completion.

Recommendations

• Create one change template (see Tutorial 4: Change templates) and have one person manage all change requests/change orders that your team creates during the tutorials.
• Enable them to create their own change template or clone an existing one where they set themselves as the change coordinator. Be sure they include their initials in the template name so they know which one is theirs.
• Have them work in groups with one change coordinator and change template per group.
• Note that the Editor [Change Approval Templates] role is used to grant access to create change approval templates. This role is applied to everyone by default, so consider who you want to have this ability. Consider also archiving change templates once they are no longer needed.
• Change templates may come with predefined tasks which are then copied to the corresponding change request and change order. In order to complete Tutorials 3 and 4 which bypass the task completion steps, the specified change coordinator on the chosen change template will need to remove any tasks added to the Task Planning tab before they can fast track the workflow to CCB review.