Thanks for letting us know we're doing a good job!
If you've got a moment, please tell us what we did right so we can do more of it.
Managing Your Amazon Chime Accounts
If you are using Amazon Chime as an individual user or as a group with no administrators, and you want to expand your pilot or proof of concept to include administrator functionality or you want to buy Amazon Chime Pro, you must create an Amazon Chime account in the AWS Management Console. You can decide whether to create a team account or enterprise account.
A team account is the easiest way to start inviting users to your organization and grant them Amazon Chime Pro permissions. You only pay for users when they host meetings. You don’t have to claim a domain, and you can invite users from any email domain that hasn't been claimed by another company. Everyone in the same team account is able to search and locate other registered Amazon Chime users in the team. A team account is also the right choice for paying for Pro users outside of your organization.
An enterprise account provides more control over your users from your company domains. It includes the ability to connect to your own identity provider or Okta SSO to authenticate and assign user permissions. If you're using your own identity provider, note that Amazon Chime supports Microsoft Active Directory.
Enterprise accounts provide full management of users within your account. This ensures that all users joining Amazon Chime through your claimed domains are included in your centrally managed Amazon Chime account. Enterprise accounts require claiming at least one email domain. Enterprise administrators can suspend and activate users, and use the full administrative capabilities of Amazon Chime, such as preventing specific users from signing in. Enterprise accounts simplify the process of adding users and are required for managing your users through a supported directory integration.
You can convert your team account to enterprise by claiming one or more email domains. After your account is converted, the ability to connect an Active Directory instance through AWS Directory Service becomes available. You can decide whether to continue to have your users sign in with Login with Amazon, or connect and authenticate via their Active Directory credentials. If you don't connect to an Active Directory, your users sign in with Login with Amazon (or an Amazon.com account). When Active Directory is set up, your users authenticate with their Active Directory credentials.
Contents
