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 ).
All members belong to a team, the "undispatched" group being the default.
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.
The three dots menu on the far right allows multiple actions.
Assign a role
Assign a role to a contributor, as described in .
Assign a team
Redirects to the 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.
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.
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.