Accounts and sign-in

Signing in

People sign in at platform.emtelligent.com with either:

• Google, using their work Google account, or
• an email address and password.

In their account settings, a person can add a second factor: an authenticator app, with recovery codes for when the app is unavailable.

The same sign-in opens Chart Review, for people who hold a Chart Review seat.

Joining an organization

Someone becomes a member of an organization in one of two ways.

By invitation

An owner or admin invites a person by email address, choosing whether they join as a member or an admin. The invitation is valid for 7 days; after that it expires and a new one has to be sent. The owner role cannot be given by invitation. An existing owner grants it to someone who is already a member.

By verified domain

If your staff share an email domain, an owner can claim that domain for your organization. Once the domain is verified, anyone who signs in with Google using an address at that domain joins your organization automatically, at the role the owner chose: member or admin.

That is a standing grant of access, so it takes two steps:

1. Claim the domain. The platform shows a DNS record to publish: a TXT record named _emtelligent-verify.<your domain>.
2. Publish the record and verify. Add the record at your DNS provider, then choose Verify on the platform. Until the record is verified, the claim grants nothing.

Public email providers such as gmail.com cannot be claimed, since anyone could join through them. Existing members are unaffected by a claim, and the owner role is never granted this way.

Automatic joining applies to sign-in with Google. People who sign in with an email address and password join by invitation.

Leaving and removing members

• Any member can leave an organization.
• Owners and admins can suspend or remove a member. Suspension is the reversible one: the person cannot use the organization on the platform or open Chart Review, and keeps their role and seat for when they are reinstated. The credentials they created keep working, so revoke those separately if that is the reason for suspending.
• When removing someone, you can revoke the credentials they created at the same time: their API keys and their OAuth clients. Credentials created by a person who has left otherwise keep working, because they belong to the organization rather than to the person.
• An organization always keeps at least one owner. The last owner cannot leave, be removed, or be changed to another role until someone else is made an owner.

See Roles and permissions for who can do each of these.