website logo
Sign upLogin
⌘K
πŸš€ Getting started
Introduction
Echoes fundamentals
Understanding Echoes data
Developer guide
Configuration guides
βš™οΈ CONFIGURATION
Outcomes
Initiatives
Members
Teams
πŸ”Œ INTEGRATIONS
Source code managers
Issue trackers
Incident management
Compatibility matrix
πŸ“Š REPORTS
Organization health
DORA metrics
πŸ€– API
Introduction
Authentication
Releases
Incidents
Efforts
Teams
πŸ”” NOTIFICATIONS
Email report
Slack notifications
πŸ‘€ ACCOUNT
Users & Roles
Single sign-on
Linking identities
Billing
πŸ₯· ADVANCED
Echoes IP addresses
Scoped publishing
Changelog
Docs powered byΒ archbeeΒ 
2min

Manual configuration

One way to configure Echoes teams is to manually edit the teams tree hierarchy in a graphical interface. Members can be dispatched into teams by manually selecting a team and then browsing the list of known members. This list of known members is built from data observed "in the wild" (for instance, in GitHub Pull-Requests authors).

A note on duplicated entries

There are situations where a name may appear twice (for instance if bob@echoeshq.com has been contributing under a secondary email sponge@example.com) and Echoes has no way to match these two identities to a single contributor.

ο»Ώ

This may hurt the readability of your Echoes dashboards and impact your billing. We therefore recommend that some compliance efforts is undertaken to clarify these data issues, or to reach out to support@echoeshq.com for help.

Updated 15 Sep 2022
Did this page help you?
Yes
No
UP NEXT
Import from CSV
Docs powered byΒ archbeeΒ 
TABLE OF CONTENTS
A note on duplicated entries