@7365admin1/layer-common 4.97.1-staging.514 → 4.97.1-staging.515

package/components/MemberMain.vue

@@ -374,7 +374,7 @@
                       v-model="selectedRole"
                       :items="pickerRoles"
                       item-value="_id"
-                      :item-title="roleLabel"
+                      :item-title="props.siteId ? sitePickerRoleLabel : roleLabel"
                       density="comfortable"
                       :rules="[requiredRule]"
                       :error-messages="
@@ -428,6 +428,7 @@ import {
   limitedSites,
   withCurrentRole,
   roleLabel,
+  sitePickerRoleLabel,
 } from "../utils/role";
 import { formatLastActive } from "../utils/last-active";
 import { formatMemberDate, memberAccess, memberPerson } from "../utils/member-row";

package/components/RolePermissionMain.vue

@@ -166,7 +166,7 @@
                 <v-select
                   v-model="memberReassignments[member._id]"
                   :items="deletionPreview.replacementRoles"
-                  :item-title="roleLabel"
+                  :item-title="props.siteId ? sitePickerRoleLabel : roleLabel"
                   item-value="_id"
                   label="Reassign role"
                   density="comfortable"
@@ -206,7 +206,7 @@
 
 <script setup lang="ts">
 // Relative import: this layer's `utils/` is not auto-imported into consumers.
-import { roleLabel, safeReturnTo, showSiteField } from "../utils/role";
+import { roleLabel, safeReturnTo, showSiteField, sitePickerRoleLabel } from "../utils/role";
 import { holdsPermission } from "../utils/permission-spellings";
 import {
   catalogueForOrg,

package/package.json

@@ -2,7 +2,7 @@
   "name": "@7365admin1/layer-common",
   "license": "MIT",
   "type": "module",
-  "version": "4.97.1-staging.514",
+  "version": "4.97.1-staging.515",
   "author": "7365admin1",
   "main": "./nuxt.config.ts",
   "//files": "What a consumer extending this layer actually loads. Without this npm ships the whole working tree - the changesets, the CI workflows, the render harness in tools/ and any scratch directory that happened to exist at publish time. Nuxt resolves a layer by directory, so every runtime directory below has to stay listed; adding a new top-level runtime directory means adding it here too.",

package/utils/invite-role-options.ts

@@ -16,7 +16,8 @@ export function inviteRoleOptions(
     .filter((role) => role && role._id)
     .map((role) => ({
       _id: String(role._id),
-      title: String(role.name ?? ""),
+      // Organisation-wide roles read "Administrator (organisation)" (owner, 2026-10-06).
+      title: role.site ? String(role.name ?? "") : `${String(role.name ?? "")} (organisation)`,
       subtitle: role.site ? SITE_ROLE_LABEL : ORG_ROLE_LABEL,
     }));
 }

package/utils/role.ts

@@ -22,6 +22,19 @@ export function roleLabel(role: { name?: unknown; siteName?: unknown; site?: unk
   return role?.site && site ? `${name} · ${site}` : name;
 }
 
+/**
+ * A site-level role picker's label (owner, 2026-10-06): organisation-wide roles
+ * stay offered at a site but read "Administrator (organisation)", so nobody
+ * mistakes them for a role of this site. Site roles keep `roleLabel`. Display
+ * only - the picker still sends the same `_id`. A row the server did not send
+ * (`withCurrentRole`'s placeholder has no `type`) is left plain: we do not know
+ * whether it is organisation-wide.
+ */
+export function sitePickerRoleLabel(role: { name?: unknown; siteName?: unknown; site?: unknown; type?: unknown } | null | undefined): string {
+  if (!role || role.site || role.type === undefined) return roleLabel(role);
+  return `${roleLabel(role)} (organisation)`;
+}
+
 /**
  * The Assign Role picker's list, with the member's CURRENT role always in it.
  *