9.2 Roles

You can assign users or groups to roles that let them plan, monitor, and execute transformation projects. Transformation Manager provides five roles: System Administrator, Project Manager, Project Architect, Migration Specialist, and Dashboard Viewer. Each role carries its own set of responsibilities in the PTM environment.

Roles can be assigned directly or inherited. Inherited roles can be set for system users or groups at the System, Organization, Project, Wave, or Batch level. Inherited roles can be set for organization users or groups at the Organization, Project, Wave, or Batch level. The inherited roles apply across all components in that level for existing and new components, as illustrated in Figure 9-1. For example, if you assign the system user account for John as the Project Manager for an organization, the organization’s existing and new projects automatically inherit the setting.

Figure 9-1 Scope of Permissions for Inherited Roles

9.2.1 System Administrator Role

The System Administrator role has full privileges in Transformation Manager. The initial user account that you create during the installation automatically has this role. You can add system users or system groups to the Administrators group to assign this role. The System Administrator typically performs the following tasks:

Configures, maintains, and monitors the health of the PTM Server.
Has all privileges throughout the product.
Has exclusive privileges to perform the following tasks:
- Create and delete organizations.
- Create and delete projects.
- Create and delete Operating System types.
- Assign users and groups to roles at the Organization level.
- Assign users and groups to the Project Manager role.
Can perform all tasks for every role in any project.

9.2.2 Project Manager Role

The Project Manager role can be a user or group. For an assigned project, this role has the permissions necessary to perform the following tasks:

Manages the project.
Creates and deletes users.
Creates and deletes non-administrator groups, and assigns members to them.
Assigns users or groups to the Project Architect, Migration Specialist, and Dashboard Viewer roles.
Tracks project progress and core statistics, using the dashboard.
Performs any of the Project Architect tasks.
- Creates and deletes waves, batches, and applications.
- Bulk imports project workloads.
- Creates and deletes resources.
- Defines proposed workloads.
- Submits workloads that are ready for transformation, or withdraws them if transformation changes are needed.

9.2.3 Project Architect Role

The Project Architect role can be user or group. For an assigned project, this role has the permissions necessary to perform the following tasks:

Views all information for the project.
Creates and deletes waves, batches, and applications.
Assigns users or groups to the Migration Specialist role for waves and batches.
Bulk imports project workloads.
Creates and deletes resources.
Defines proposed workloads.
Submits workloads that are ready for transformation, or withdraws them if transformation changes are needed.
Tracks project progress and core statistics, using the dashboard.
Can execute the individual migrations, according to the project plan.

9.2.4 Migration Specialist Role

The Migration Specialist role can be a user or group. For an assigned project, wave or batch, this role has the permissions necessary to perform the following tasks:

Views information for the project’s waves, batches, and workloads.
Views information for the project’s resources.
Executes the individual migrations, according to the project plan.
Tracks project progress and core statistics, using the dashboard.

9.2.5 Dashboard Viewer Role

The Dashboard Viewer role can be a user or group. The Dashboard Viewer role has the permissions necessary to view the dashboard information only for an assigned organization, project, wave, or batch. Inherited permissions apply to this role in the child containers if you assign this role at the system, organization, project, wave, or batch level.