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Β 
7min

Members

Members in Echoes terminology are all the people participating in your organization.

ο»Ώ

A member may be mapped to multiple identities across integrations, such as a GitHub login, or a JIRA account. A member may have an Echoes account, in which case a role is associated to it (see Users & Roles).

ο»Ώ

All members belong to a team, the "undispatched" group being the default.

ο»Ώ

Members sidebar menu
Members sidebar menu

The top toolbar allows for searching among members by name or email as well as provides a direct access to the invite page via the Invite button.

Members management page
Members management page

The three dots menu on the far right allows multiple actions.

Assign a role

Assign a role to a contributor, as described in Users & Roles.

Member role assignment
Member role assignment

Assign a team

Redirects to the teams page in order to dispatch the member into another team.

ο»Ώ

ο»Ώ

View participation history

Examine the trajectory of the member throughout the organization over time. This is important as a member's contribution are attributed to their team of belonging at the time the work was done.

Member participation history
Member participation history

Frequently asked questions

Q: Can a member belong to more than one team?

No, a member can only belong to one team at a time. We generally recommend assigning members to their "primary" team, knowing that it's possible to capture through outcomes and initiatives that they contribute to broader goals. Alternatively, it's possible to add members to non-leaf nodes of the organization tree, therefore effectively having their participation span across multiple teams.

Q: What happens to past contributions when a member changes team?

Past contributions are not impacted by a change of team, only future contributions do. It is however possible to edit a member's join date within a team, which may reattribute some of their past contributions to the appropriate team.

Updated 20 Oct 2022
Did this page help you?
Yes
No
UP NEXT
Teams
Docs powered byΒ archbeeΒ 
TABLE OF CONTENTS
Assign a role
Assign a team
View participation history
Frequently asked questions
Q: Can a member belong to more than one team?
Q: What happens to past contributions when a member changes team?