Team members vs portal members (important distinction)

Project Echo has two different kinds of people. Mixing them up causes confusion about access, invitations, and who appears where.

Team members (workspace teammates)

Team members work inside app.projectecho.io. They triage requests, update the roadmap, publish changelog entries, and change settings.

Managed under Settings → Team
Join by email invitation
Can invite other teammates
Billing admins can disable or delete teammates (with safeguards for the last billing admin)

Think of team members as your internal product, support, and engineering collaborators.

Portal members are customers or end users associated with your feedback portal—not full workspace teammates.

Browse them under Members in the sidebar (not under Settings)
May be created manually or arrive through your product embed / external user id
Interact on https://YOURSUBDOMAIN.projectecho.io (submit, vote, comment when they have member access)
Do not get staff-app settings access by default

	Team members	Portal members
Primary home	Staff app	Feedback portal
Managed in	Settings → Team	Sidebar → Members
Typical role	Internal staff	Customers / end users
Can change workspace settings	Yes (per permissions)	No

Invite a coworker via Settings → Team, not Members.
Track customer activity under Members.
Portal visibility modes that mention “members” refer to portal members (plus teammates), not “anyone with an email.”

More detail: manage invitations under Team, and browse activity under Members. Help: [email protected].