Preview · This help is still growing and will be extended over time.
Sign in to Abacus
Connect your personal Abacus account to echo
So that echo can show you the matching information from Abacus, you connect echo once with your personal Abacus account. This user connection only applies to you. You set it up under Settings → My accounts.
Sign in
Open My accounts
In Teams, open echo's Settings tab and click My accounts under Personal. Scroll to the Abacus section.
Sign in with your Abacus account
Click 1 Login and sign in with your personal Abacus credentials. Afterwards the section shows your name with the status Connected.
Logout removes your connection again. echo then no longer searches Abacus for you, unless your organization uses a shared connection.
Shared connection of your organization
Your administrator can set up one shared Abacus connection for everyone who has not signed in personally (see Shared connection). Then the section says You are using the shared connection of your organization. You can still click Sign in with your own user. If you log out of your own user later, echo uses the shared connection again.
Required permissions
Your Abacus user needs a CRM license and the API scopes for the data echo reads. Your Abacus administrator grants them in the Abacus user management (program Q981). For contact search, Read subjects and Read connections are enough. Other scopes are only needed for the related feature, for example service orders or activities. The full list is in Configure the Abacus integration.
Troubleshooting
“Your Abacus connection has expired.” Open Settings → My accounts, click Login in the Abacus section and sign in again.
“Missing scopes”. Ask your administrator to grant the listed scopes in Q981. Then click Logout and Login again.
“Access denied” when searching. echo lists what to check: the echo integration in Abacus (Q910), your CRM license and your scopes (Q981). Ask your Abacus administrator.