**End of support notice**: On February 20, 2026, AWS will end support for the Amazon Chime service. After February 20, 2026, you will no longer be able to access the Amazon Chime console or Amazon Chime application resources. For more information, visit the [blog post](https://aws.amazon.com/blogs/messaging-and-targeting/update-on-support-for-amazon-chime/). **Note:** This does not impact the availability of the [Amazon Chime SDK service](https://aws.amazon.com/chime/chime-sdk/).
# Managing users
**Note**
The steps in this section assume that you have a set of user email addresses, or that you've connected your administrator account to Active Directory. For more information, refer to [Connecting to your Active Directory](active_directory.md), in this guide.
You use the Amazon Chime console to add and manage users. You add users by inviting them. As they accept your invitations, they appear under **Users**, which lists all the users in your account and their user details. For more information, see [Viewing user details](user-details.md).
Administrators of accounts using **Login with Amazon** (LWA) also see options to manage permission tiers and remove users from an account. These actions are managed through Active Directory or Okta, depending on which one of those you configure an account to use. For more information, see [Managing user permissions and access](manage-access.md).
**Topics**
+ [Adding users](adding-users.md)
+ [Viewing user details](user-details.md)
+ [Managing user permissions and access](manage-access.md)
+ [Changing personal meeting PINs](change-PINs.md)
+ [Managing Pro trials](manage-protrials.md)
+ [Requesting user attachments](request-attachments.md)
+ [How Amazon Chime manages automatic updates](managing-auto-update.md)
+ [Migrating users to another Team account](migrate-users.md)
# Adding users
You add users to an Amazon Chime account by inviting them to join the account. You send invitations to potential users from the Amazon Chime console, and these steps explain how.
1. Open the Amazon Chime console at [https://chime.aws.amazon.com/](https://chime.aws.amazon.com).
A list of the accounts that you administer appears.
1. Choose the account to which you want to add members, then choose **Invite users**.
The **Invite new users** dialog box appears.
1. Enter the email addresses of the users that you want to invite. Separate each address with a semicolon (;).
1. Choose **Invite users**.
The new users appear in the list. When you invite users to a Team account, their details won't appear until they accept your invitation.
# Viewing user details
In the Amazon Chime console, under **Users**, you can view a list of all the users in your account and see their user details. Search for a specific user by their email address and choose their name to see their user details. Under **User details**, you can see detailed information about the user, and make updates to their user account.
The following table lists the user details that appear in the console.
**Note**
Complete user details don't appear for Team account users until after they accept their invites.
| Field | Description | Example |
| --- | --- | --- |
| Display name | The user's name that appears in Amazon Chime. For Login with Amazon (LWA) users, this is the full name. For Active Directory users, the DISPLAY\$1NAME\$1ATTRIBUTE is used. | Major, Mary |
| Email address | For LWA users, the email address used for registration. For Active Directory users, the primary email address from Active Directory appears. | mary.major@example.com |
| Registration | The user’s current registration status. The possible values are different between Enterprise accounts, where invitations are not sent, and Team accounts, where invitations are sent. | Registered, Unregistered (for a Team account), or Suspended (for an Enterprise account) |
| Permission tier | Set to Pro by default, to allow users to host meetings. It can be changed to Basic. | Pro, Basic |
| Invited | For Team accounts, the date when the user was invited to the account. | 01/05/2020 |
| Joined | The date when the user first signed into Amazon Chime. For Pro trial users, this is also the date that their Pro trial began. | 01/10/2020 |
| Personal PIN | The personal meeting PIN that the user can use to schedule meetings. | 0123456789 |
| Privacy setting | The presence setting that the user selected. | Public or Private |
| Meetings attended | The number of meetings that a user has attended. | 87 |
| Meetings organized | The number of meetings that a user has organized. | 12 |
| Meeting satisfaction | The percentage of positive responses given to the end-of-meeting survey. | 92% |
| Last active date | The date when the user was last active. | 06/12/2020 |
| Chat messages sent | The number of chat messages the user sent. | 1025 |
| Phone number | The phone number assigned to a user, if any. | \$112065550100 |
# Managing user permissions and access
Manage which features your Amazon Chime users can access by assigning them Pro or Basic permissions. Users with Basic permissions cannot host meetings, but they can attend meetings and use chat. For more information about the features that users with Pro and Basic permissions can access, see [Plans and pricing](https://aws.amazon.com/chime/pricing).
Manage who can sign into your Amazon Chime administrative account by inviting or suspending users. Only Enterprise account administrators can suspend users. Team account administrators can remove users from their accounts so that they are no longer paying for the user’s permissions. However, they can't suspend the user to prevent them from signing in. For more information about the differences between Enterprise and Team accounts, see [Managing your Amazon Chime accounts](manage-chime-account.md).
## Managing user permissions
As an Amazon Chime administrator, you can manage Pro and Basic permissions for the users in your Amazon Chime account.
If Active Directory or Okta is configured for your Amazon Chime account, manage user permissions through their directory group membership. If you do not have Active Directory or Okta configured, manage user permissions from the Amazon Chime console.
### Team accounts and Enterprise Login with Amazon
If you administer an Amazon Chime Team account or Enterprise LWA account, where users sign in with their Login with Amazon (LWA) accounts, you can manage Pro and Basic permissions in the Amazon Chime console.
**To manage user permissions for Team and Enterprise LWA accounts**
1. Open the Amazon Chime console at [https://chime.aws.amazon.com/](https://chime.aws.amazon.com).
1. For **Accounts**, choose the name of the Amazon Chime account.
1. Choose **Users**.
1. Select the users and choose **Actions**, **Assign permissions**.
1. Choose one of the following permissions:
+ **Pro**
+ **Basic**
1. Choose **Assign**.
### Enterprise Active Directory or Enterprise OpenID Connect (Okta) accounts
If your users sign in with Active Directory or Okta credentials, manage their permissions by making them members of a directory group that has Pro or Basic permissions assigned to it.
To assign Pro permissions to a user, make them a member of an Active Directory or Okta group that you have assigned Pro permissions to. To assign Basic permissions to a user, make them a member of a group that you have assigned Basic permissions to. Users who don't have either Pro or Basic permissions aren't able to sign into Amazon Chime.
## Managing user access
If you administer an Amazon Chime account, you can invite users to allow to them to sign in to your account. Enterprise account administrators can suspend user access to prevent them from signing in to the account.
### Inviting and removing Team account users
If you administer a Team account, use the Amazon Chime console to invite users from any email domain.
**Note**
A user's free 30-day Pro trial ends when they accept your invitation.
**To invite users to a Team account**
1. Open the Amazon Chime console at [https://chime.aws.amazon.com/](https://chime.aws.amazon.com).
1. For **Accounts**, choose the name of the Team account.
1. Choose **Users**, **Invite users**.
1. Enter the email addresses of the users to invite, separating multiple email addresses with a semicolon (**;**).
1. Choose **Invite users**.
The following procedure disassociates users from your Team account by removing any Pro or Basic permissions assigned to them. Removed users can still sign in to Amazon Chime, but they are no longer paid members of your Amazon Chime account.
**To remove users from a Team account**
1. Open the Amazon Chime console at [https://chime.aws.amazon.com/](https://chime.aws.amazon.com).
1. For **Accounts**, choose the name of the Team account.
1. Choose **Users**.
1. Select the users to remove and choose **Actions**, **Remove user**.
Any Pro or Basic permissions assigned to the users are removed. The users can no longer use autocomplete to find new Team users in their **Contacts**.
### Inviting and suspending Enterprise account users
If you administer an Enterprise account, any users that register for Amazon Chime with an email address from your claimed domains are automatically added to your account. If you configured Active Directory or Okta, the users must also be members of the directory group you configured for Amazon Chime.
**To invite users to an Enterprise account**
+ Send an invitation email to the users in your organization and instruct them to follow the steps in [Creating an Amazon Chime account](https://docs.aws.amazon.com/chime/latest/ug/chime-create-account.html) in the *Amazon Chime User Guide*.
Users sign in with an email address from one of the domains that you claimed for your account. After they complete the steps to create their Amazon Chime user accounts, they automatically appear under your Enterprise account **Users** in the Amazon Chime console.
The following procedure suspends users from an Enterprise account that does not have Active Directory or Okta configured. This prevents the users from signing in to Amazon Chime.
**To suspend users from an Enterprise account**
1. Open the Amazon Chime console at [https://chime.aws.amazon.com/](https://chime.aws.amazon.com).
1. For **Accounts**, choose the name of the Enterprise account.
1. Choose **Users**.
1. Select the users to suspend and choose **Actions**, **Suspend user**.
1. Select the check box and choose **Suspend**.
If you have Active Directory or Okta configured for your Enterprise account, use the following procedure to suspend users.
**To suspend users from an Enterprise Active Directory or OpenID Connect (Okta) account**
+ Do one of the following:
+ From your Active Directory or Okta Administrator Dashboard, suspend the user or mark them inactive.
+ Remove the user from any Active Directory group that has Basic or Pro permissions assigned to it.
# Changing personal meeting PINs
A personal meeting PIN is a static ID generated when the user registers. The PIN makes it easy for an Amazon Chime user to schedule meetings with other Amazon Chime users. Using a personal meeting PIN means that meeting organizers don't have to remember meeting details for each new meeting that they schedule.
If a user feels that their personal meeting PIN has been compromised, you can reset their PIN and generate a new ID. After you update a personal meeting PIN, the user must update all meetings that were scheduled using the old personal meeting PIN.
**To change a personal meeting PIN**
1. Open the Amazon Chime console at [https://chime.aws.amazon.com/](https://chime.aws.amazon.com).
1. On the **Accounts** page, select the name of the Amazon Chime account.
1. In the navigation pane, choose **Users**.
1. Search for the user who needs their PIN changed.
1. To open the **User detail** page, choose the name of the user.
1. Choose **User actions**, **Reset personal PIN**, **Confirm**.
# Managing Pro trials
When a user accepts an Amazon Chime Team invitation or is added to an Enterprise account, their free trial ends and they have Pro permissions. This enables them to continue to host meetings that are scheduled. Changing a user’s permission tier to Basic prevents them from acting as a meeting host.
With Amazon Chime usage-based pricing, you only pay for users that host meetings on the days that they host them. Meeting attendees and chat users are not charged.
Pro users are considered Active Pro if they hosted a meeting that ended on a calendar day and at least one of the following occurred:
+ The meeting was scheduled.
+ The meeting included more than two attendees.
+ The meeting had at least one recording event.
+ The meeting included an attendee that dialed in.
+ The meeting included an attendee that joined with H.323 or SIP.
For more information, see [Plans and Pricing](https://aws.amazon.com/chime/pricing).
# Requesting user attachments
If you manage an Enterprise account and have the appropriate permissions, you can request and receive the attachments that your users upload into Amazon Chime. You can get attachments that users uploaded into 1:1 and group conversations, or into chat rooms that they created.
**Note**
If you manage an Amazon Chime Team account, you can upgrade to an Enterprise account by claiming one or more domains. Alternatively, you can remove users from the Team account, which enables those unmanaged users to get their attachments using the Amazon Chime Assistant.
**To request user attachments**
1. Open the Amazon Chime console at [https://chime.aws.amazon.com/](https://chime.aws.amazon.com).
1. On the **Accounts** page, select the name of the Amazon Chime account.
1. Under **Settings**, choose **Account**, **Account actions**, **Request attachments**.
1. Within approximately 24 hours, the **Account summary** page provides a link to a file containing a list of presigned URLs that you use to access each attachment.
1. Download the file.
**Note**
Be sure to maintain an appropriate level of access control on the file. Any user that obtains the file can use the provided list of URLs to download the associated attachments.
Presigned URLs expire after 6 days. You can submit a request one time every 7 days.
To use AWS Identity and Access Management (IAM) policies to manage access to the Amazon Chime administration console and the **Request attachments** action, use one of the Amazon Chime managed policies (FullAccess, UserManagement, or ReadOnly). Alternatively, you can update the custom policies to include the `StartDataExport` action and `RetrieveDataExport` action. For more information about these actions, see [Actions defined by Amazon Chime](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_amazonchime.html#amazonchime-actions-as-permissions) in the *IAM User Guide*.
# How Amazon Chime manages automatic updates
Amazon Chime provides different ways to update its clients. The method varies, depending on whether you run Amazon Chime in a browser, on your desktop, or on a mobile device.
The Amazon Chime web application – [https://app.chime.aws](https://app.chime.aws) – always loads with the latest features and security fixes.
The Amazon Chime desktop client checks for updates whenever you choose **Quit** or **Sign Out**. This applies to Windows and macOS machines. As you run the client, it checks for updates every three hours. You can also check for updates by choosing **Check for Updates** on the Windows Help menu or on the macOS **Amazon Chime** menu.
When the desktop client detects an update, Amazon Chime prompts user to install it unless they're in an ongoing meeting. They're in an *ongoing meeting* when:
+ They attend a meeting.
+ They were invited to a meeting that is still in progress.
Amazon Chime prompts them to install the latest version, and it provides a 15-second countdown so they can postpone the installation. Users choose **Try Later** to postpone the update.
If users postpone an update, and they aren't in an ongoing meeting, the client checks for the update after three hours and prompts them again to install. The installation begins when the countdown ends.
**Note**
On a macOS machine, users need to choose **Restart Now** to begin the update.
**On mobile devices** – Amazon Chime mobile applications use the update options provided by the App Store and Google Play to deliver the latest version of the Amazon Chime client. You can also use mobile device management system to deploy updates.
# Migrating users to another Team account
You migrate users to other Team accounts by creating and configuring a destination account, if one doesn't already exist. Then you add users to the destination account. The following steps take you to information about completing each part of a migration.
**To migrate users**
1. If you don't have a destination Team account, create one. For more information, see [Step 1: Creating an Amazon Chime administrator account](getting-started.md#create-account).
1. As needed, configure the account. For more information, see [Step 2 (optional): Configuring account settings](getting-started.md#acct-settings).
1. Add users to the account. For more information, see [Step 3: Adding users to your account](getting-started.md#add-users).