# Roles<a name="roles"></a>

AWS MigOps defines five roles: `MigrationSpaceAdmin`, `MigrationSpaceContributor`, `JourneyAdmin`, `JourneyContributor`, and `TeamContributor`\. This topic explains how to assign these roles\. For the permissions that are associated with each of the five roles, see [Permissions](permissions-table.md)\.

**Important**  
When you edit the role of a team or an individual, it can take up to 5 minutes for the role change to take effect after you see the change in the console\.

## MigrationSpaceAdmin<a name="migration-space-admin"></a>

When you create a migration space, you automatically get the `MigrationSpaceAdmin` for that space\. When you're a `MigrationSpaceAdmin`, you can also grant this role to others\.

**To grant the `MigrationSpaceAdmin` role to an individual that is already a member of the migration space**

1. In the navigation pane, choose **Migration spaces**\.

1. Choose the name of the migration space to which you want to give the individual the `MigrationSpaceAdmin` role\.

1. Choose the **Individuals** tab\.

1. Choose the radio button next to the name of the individual to whom you want to give the `MigrationSpaceAdmin` role\.

1. Choose **Edit role**\.

1. In the dialog box, choose the **MigrationSpaceAdmin** option\.

1. Choose **Save**\.

**To grant the `MigrationSpaceAdmin` role to an individual that isn't already a member of the migration space**

1. In the navigation pane, choose **Migration spaces**\.

1. Choose the name of the migration space to which you want to give the individual the `MigrationSpaceAdmin` role\.

1. Choose the **Individuals** tab\.

1. Choose **Invite**\.

1. Enter the individual's email address and choose the **MigrationSpaceAdmin** option\.

1. Choose **Invite**\.

**To grant the `MigrationSpaceAdmin` role to a team that is already a member of the migration space**

1. In the navigation pane, choose **Migration spaces**\.

1. Choose the name of the migration space to which you want to give the individual the `MigrationSpaceAdmin` role\.

1. Choose the **Teams** tab\.

1. Choose the radio button next to the name of the team to which you want to give the `MigrationSpaceAdmin` role\.

1. Choose **Edit role**\.

1. In the dialog box, choose the **MigrationSpaceAdmin** option\.

1. Choose **Update**\.

**To grant the `MigrationSpaceAdmin` role to a team that isn't already a member of the migration space**

1. In the navigation pane, choose **Migration spaces**\.

1. Choose the name of the migration space in which you want to create a team and to make that team a `MigrationSpaceAdmin`\.

1. Choose the **Teams** tab\.

1. Choose **Create team**\.

1. Enter a name and an optional description for the team, and choose the **MigrationSpaceAdmin** option\.

1. Choose **Create**\.

## MigrationSpaceContributor<a name="migration-space-contributor"></a>

A `MigrationSpaceAdmin` can invite an individual to become a `MigrationSpaceContributor` in that space\. The `MigrationSpaceAdmin` can also create a new team and give it the `MigrationSpaceContributor` in that space\. In addition, a `MigrationSpaceAdmin` can change the role of a team or an individual from `MigrationSpaceAdmin` to `MigrationSpaceContributor`\.

**To invite an individual to become a `MigrationSpaceContributor`**

1. In the navigation pane, choose **Migration spaces**\.

1. Choose the name of the migration space to which you want to give the individual the `MigrationSpaceContributor` role\.

1. Choose the **Individuals** tab\.

1. Choose **Invite**\.

1. Enter the individual's email address and choose the **MigrationSpaceContributor** option\.

1. Choose **Invite**\.

1. Notify the individual to whom you sent the invitation that they will receive an email from the following address: `no-reply@es.prod.us-east-2.service.migops.migration-services.aws.dev`

   The body of the email will have a **Respond** button that they can use to accept or reject the invitation\.

   In addition to the invitation email, the individual can also go to **Pending actions** to see the invitation that you sent them and to accept it or reject it\. For more information, see [Pending actions](pending-actions.md)\.
**Important**  
For the recipient of the invitation to get the `MigrationSpaceContributor` role, they must accept the invitation that you sent them\. To accept the invitation, they can choose **Respond** in the invitation email, or they can go directly to **Pending actions** in the AWS MigOps console\. For more information, see [Pending actions](pending-actions.md)\. 

**To create a team and give it the `MigrationSpaceContributor` role**

1. In the navigation pane, choose **Migration spaces**\.

1. Choose the name of the migration space in which you want to create the team\.

1. Choose the **Teams** tab\.

1. Choose **Create team**\.

1. Enter a name and an optional description for the team, and choose the **MigrationSpaceContributor** option\.

1. Choose **Create**\.

**To change the role of an individual from `MigrationSpaceAdmin` to `MigrationSpaceContributor`**

1. In the navigation pane, choose **Migration spaces**\.

1. Choose the name of the migration space in which you want to make the change\.

1. Choose the **Individuals** tab\.

1. Choose the radio button next to the individual whose role you want to change\.

1. Choose **Edit role**\.

1. Choose the **MigrationSpaceContributor** option\.

1. Choose **Update**\.

**To change the role of a team from `MigrationSpaceAdmin` to `MigrationSpaceContributor`**

1. In the navigation pane, choose **Migration spaces**\.

1. Choose the name of the migration space in which you want to make the change\.

1. Choose the **Teams** tab\.

1. Choose the radio button next to the team whose role you want to change\.

1. Choose **Edit role**\.

1. Choose the **MigrationSpaceContributor** option\.

1. Choose **Update**\.

## JourneyAdmin<a name="journey-admin"></a>

A `MigrationSpaceAdmin` or a `JourneyAdmin` can make an individual or a team a `JourneyAdmin`\.

**To grant the `JourneyAdmin` role to an individual or a team that is already a member of the migration journey**

1. In the navigation pane, choose **Migration journeys**\.

1. Choose the name of the migration journey to which you want to give the individual or team the `JourneyAdmin` role\.

1. Choose the **Individuals and teams** tab\.

1. Choose the radio button next to the individual or team to whom you want to give the `JourneyAdmin` role\.

1. Choose **Edit role**\.

1. In the dialog box, choose the **JourneyAdmin** option\.

1. Choose **Save**\.

**To grant the `JourneyAdmin` role to an individual or a team that isn't already a member of the migration journey**

1. In the navigation pane, choose **Migration journeys**\.

1. Choose the name of the migration journey to which you want to give the individual or team the **JourneyAdmin** role\.

1. Choose the **Individuals and teams** tab\.

1. Choose **Invite**\.

1. Specify the email address of the individual or team that you want to invite\.

1. Under **Role**, choose the **JourneyAdmin** option\.

1. Choose **Invite**\.

1. Notify the individual to whom you sent the invitation that they will receive an email from the following address: `no-reply@es.prod.us-east-2.service.migops.migration-services.aws.dev`

   The body of the email will have a **Respond** button that they can use to accept or reject the invitation\.

   In addition to the invitation email, the individual can also go to **Pending actions** to see the invitation that you sent them and to accept it or reject it\. For more information, see [Pending actions](pending-actions.md)\.
**Important**  
For the recipient of the invitation to get the `JourneyAdmin` role, they must accept the invitation that you sent them\. To accept the invitation, they can choose **Respond** in the invitation email, or they can go directly to **Pending actions** in the AWS MigOps console\. For more information, see [Pending actions](pending-actions.md)\. 

## JourneyContributor<a name="journey-contributor"></a>

A `MigrationSpaceAdmin` or a `JourneyAdmin` can invite an individual or a team to become a `JourneyContributor`\.

**Important**  
If an individual or a team is a `JourneyContributor` in a journey, but a `MigrationSpaceAdmin` in the migration space that contains that journey, then that individual or team is effectively a `JourneyAdmin` of that journey\. Their role will appear as `JourneyContributor`, but they will be able to perform all the actions that a `JourneyAdmin` has the permissions to perform\.

**To grant the `JourneyContributor` role to an individual or a team that is already a member of the migration journey**

1. In the navigation pane, choose **Migration journeys**\.

1. Choose the name of the migration journey to which you want to give the individual or team the `JourneyContributor` role\.

1. Choose the **Individuals and teams** tab\.

1. Choose the radio button next to the individual or team to whom you want to give the `JourneyContributor` role\.

1. Choose **Edit role**\.

1. In the dialog box, choose the **JourneyContributor** option\.

1. Choose **Save**\.

**To grant the `JourneyContributor` role to an individual or a team that isn't already a member of the migration journey**

1. In the navigation pane, choose **Migration journeys**\.

1. Choose the name of the migration journey to which you want to give the individual or team the `JourneyContributor` role\.

1. Choose the **Individuals and teams** tab\.

1. Choose **Invite**\.

1. Specify the email address of the individual or team that you want to invite\.

1. Under **Role**, choose the **JourneyContributor** option\.

1. Choose **Invite**\.

1. Notify the individual to whom you sent the invitation that they will receive an email from the following address: `no-reply@es.prod.us-east-2.service.migops.migration-services.aws.dev`

   The body of the email will have a **Respond** button that they can use to accept or reject the invitation\.

   In addition to the invitation email, the individual can also go to **Pending actions** to see the invitation that you sent them and to accept it or reject it\. For more information, see [Pending actions](pending-actions.md)\.
**Important**  
For the recipient of the invitation to get the `JourneyContributor` role, they must accept the invitation that you sent them\. To accept the invitation, they can choose **Respond** in the invitation email, or they can go directly to **Pending actions** in the AWS MigOps console\. For more information, see [Pending actions](pending-actions.md)\. 

## TeamContributor<a name="team-contributor"></a>

A `MigrationSpaceAdmin` can invite an individual to become a `TeamContributor`\.

**To invite an individual to become a `TeamContributor`**

1. In the navigation pane, choose **Migration spaces**\.

1. Choose the name of the migration space to which you want to give the individual or team the `TeamContributor` role\.

1. Choose the **Teams** tab\.

1. Choose the name of the team to which you want to invite an individual\.

1. Choose **Invite**\.

1. Specify the email address of the individual that you want to invite\.

1. Choose **Invite**\.

1. Notify the individual to whom you sent the invitation that they will receive an email from the following address: `no-reply@es.prod.us-east-2.service.migops.migration-services.aws.dev`

   The body of the email will have a **Respond** button that they can use to accept or reject the invitation\.

   In addition to the invitation email, the individual can also go to **Pending actions** to see the invitation that you sent them and to accept it or reject it\. For more information, see [Pending actions](pending-actions.md)\.
**Important**  
For the recipient of the invitation to get the `TeamContributor` role, they must accept the invitation that you sent them\. To accept the invitation, they can choose **Respond** in the invitation email, or they can go directly to **Pending actions** in the AWS MigOps console\. For more information, see [Pending actions](pending-actions.md)\.