Preview · This help is still growing and will be extended over time.

Settings · Administrator

User administration

Decide who may set up echo for your organization, and what everyone else can do

Updated: November 2026

echo knows two roles: administrators and users. Administrators set up echo for the whole organization. Users work with echo: they search contacts, see who is calling and adjust their own settings.

You manage the administrators in Settings → User Administration. Only administrators see this page. Users don't need a role in echo: everyone in your organization who opens echo in Teams is a user. What to check when a new colleague joins is described below.

The echo administrator role is separate from your Microsoft 365 roles. A Teams or Global Administrator is not automatically an echo administrator, and an echo administrator needs no Microsoft 365 admin role.

What each role can do

AdministratorUser
Search contacts, see caller information, use call history, call notes and activitiesYesYes
Personal settings (Personal group): own sign-ins and shared mailboxes under My accounts, telephony options, start page, demo modeYesYes
Add, configure and remove integrationsYesNo
Set up Quick LinksYesNo
Organization-wide telephony settings and call queuesYesNo
Manage the subscriptionYesNo
Add and remove administratorsYesNo

The settings menu has two groups. Personal is shown to everyone. Organization (integrations, Quick Links, the organization's telephony settings, user administration, subscription) is only shown to administrators; users who open such a page through an old link land on My accounts instead, or on their own Telephony Integration page for the organization's telephony settings.

What users can adjust themselves is described in Personal settings.

Who becomes the first administrator

The person who opens the setup wizard when echo is set up for the first time becomes an administrator automatically, so they can finish the setup. After the setup is complete, new administrators are only added in Settings → User Administration.

Good to know

Anyone who opened the setup wizard before it was completed is an administrator. Check the list once the setup is done and remove anyone who shouldn't be on it.

Add administrators

1

Open User Administration

In Teams, open echo's Settings tab and click User Administration.

Fig. 1: Settings → User Administration: the list of administrators and the button to add more.
2

Choose the people

Click 1 Add additional administrators. The Teams people picker opens. Select one or more colleagues and confirm.

The new administrators appear in the list right away. People who are already administrators are skipped.

3

Let them reload echo

The new administrators see the admin settings the next time they open echo. If echo is already open, they reload it once.

Remove an administrator

Click 2 Remove next to the person. They keep using echo as a user.

You can't remove yourself: your own entry shows You – already an administrator instead of a button. To give up your administrator role, ask another administrator to remove you.

Recommendation: at least two administrators

Keep at least two administrators. If your only administrator leaves the company or is on holiday, nobody can change integrations or organization-wide settings, and nobody can add a new administrator.

Administrators and licenses

The administrator role doesn't need a separate license. Licenses count the people who use echo, administrators included. You don't assign licenses to individual people. How to add licenses is described in Manage your subscription.

A new colleague joins

Users need no role in echo, but check these four things:

  1. echo is in their Teams. If you distribute echo with a setup policy, make sure the colleague is covered (Add echo to Teams).
  2. A free license. Raise the number of licenses if needed (Manage your subscription).
  3. The desktop app for caller recognition while the phone rings (Telephony integration).
  4. Their own sign-in for integrations with a personal connection, for example Abacus or Bexio. echo shows them a banner the first time (Personal settings).

Troubleshooting

“The application is not configured for use yet.” echo shows this page as long as the initial setup isn't finished. Users can't do anything here; their administrator completes the setup. The person who clicks Let's finish the setup here opens the setup wizard and becomes an administrator (see Initial setup).

A user doesn't know who the administrators are. At the bottom of Settings → My accounts, echo shows non-administrators a note with the list of all administrators.

“An error occurred while adding the administrators.” Only administrators can add or remove administrators. Reload echo and try again. If the error persists, check whether you are still on the list.

User Administration is missing from the settings menu. You are not an administrator. Ask one of your administrators to add you.

A new administrator doesn't see the Organization group. Reload echo in Teams so it picks up the new role.