Several bugs in the external stakeholder invite flow
A cluster of bugs in the external stakeholder invite flow could cause invitations to fail silently, land in the wrong inbox, or expose internal team details to external collaborators.
A cluster of bugs in the external stakeholder invite flow could cause invitations to fail silently, land in the wrong inbox, or expose internal team details to external collaborators.
The following issues are resolved:
Invite sent before you clicked Send. Clicking a permission option in the invite modal was triggering an early form submission. The invite now only sends when you click the Send button.
Mixed-case email addresses weren't matched correctly. If a collaborator's email address contained uppercase letters, the lookup could fail to find their account, meaning they wouldn't receive the correct access. Email matching is now case-insensitive.
Invitation emails arrived in ALL CAPS. The email address shown in the body of the invitation email now reflects the address exactly as entered, in lowercase.
"Add people" opened the wrong tab. Clicking Add people in the team popover was landing on the Org Members tab instead of the External Stakeholders tab, requiring an extra click to get to the right place. It now opens directly on External Stakeholders.
Three-dot menu was clipped in the External Stakeholders table. Opening the action menu for a stakeholder in project settings could cause the menu to be cut off by the table boundary. It now renders fully regardless of the row's position in the table.
Email logo wasn't visible in Gmail or Outlook. The logo in all invitation and notification emails was an SVG file, which major email clients don't display. It has been converted to a PNG and is now visible across clients.
Internal member details were visible to external collaborators. When an external stakeholder opened the team popover, they could see internal members' names and roles. Internal entries are now shown only as a role label (Admin or Member) with access details restricted.