@colixsystems/widget-sdk 0.193.0 → 0.195.0

package/README.md

@@ -60,9 +60,9 @@ The data layer lives in **four separate domain-client packages**, each instantia
 | **FILES** (`ctx.assets`) | `useAsset(id)` | `{ url, file, loading, error, refetch }` | `ctx.assets.get` — no scope |
 | **FILES** | `useAssetsByTag(tag, { type })` (optional: the whole argument, and `type` within it) | `{ assets, loading, error, refetch }` | `ctx.assets.list` (unwraps `{ data, meta }` to `assets`) — no scope. `type` defaults to `"image"`; pass `"all"` / `"audio"` / `"video"` / `"document"` to widen. Falsy `tag` collapses to `assets: []` without a round-trip. |
 | **DIRECTORY** (`ctx.directory`) | `useDirectory(query)` (optional: query) | `{ users, loading, error, refetch }` | `directory.users.list` — `directory.read:users` |
-| **DIRECTORY** | `useUsers(query)` (optional: query) | `{ users, loading, error, refetch, invite, deactivate, reactivate, remove, sendPasswordReset }` | `directory.users.*` — `users.read:*` plus the `users.read` (or `users.write`) capability, else `FORBIDDEN` (edits, incl. `sendPasswordReset()`, also `users.write:*`; `remove()` also `users.delete:*`) |
+| **DIRECTORY** | `useUsers(query)` (optional: query) | `{ users, loading, error, refetch, invite, deactivate, reactivate, remove, sendPasswordReset, update }` | `directory.users.*` — `users.read:*` plus the `users.read` (or `users.write`) capability, else `FORBIDDEN` (edits, incl. `sendPasswordReset()` and `update()`, also `users.write:*`; `remove()` also `users.delete:*`) |
 | **DIRECTORY** | `useGroups(query)` (optional: query) | `{ groups, loading, error, refetch, create, remove, addMember, removeMember }` | `directory.groups.*` — `groups.read:*` (mutations also `groups.write:*`) |
-| **DIRECTORY** | `useInvites(query)` (optional: query) | `{ invites, loading, error, refetch, resend, revoke }` | `directory.invites.*` — `users.write:*` + the SystemAcl `users.write` capability (the whole invite surface, list included). `query` is `{ status?, q?, app_user_id?, limit?, offset? }` with `status` ∈ `pending \| accepted \| revoked \| expired \| not_sent \| open \| all` (endpoint default `all`; `open` = `pending`, `not_sent` or `expired`); `q` matches the invite's name or email, `app_user_id` returns the invites reserving that user id. `resend(inviteId)` sends the invitation — the first send of a `not_sent` one included. |
+| **DIRECTORY** | `useInvites(query)` (optional: query) | `{ invites, loading, error, refetch, resend, revoke }` | `directory.invites.*` — `users.write:*` + the SystemAcl `users.write` capability (the whole invite surface, list included). `query` is `{ status?, q?, app_user_id?, limit?, offset? }` with `status` ∈ `pending \| accepted \| revoked \| expired \| open \| all` (endpoint default `all`; `open` = `pending` or `expired`); `q` matches the invite's name or email, `app_user_id` returns the invites reserving that user id. |
 | **DIRECTORY** | `useBankIdLink()` | `{ linked, available, status, qr, message, startLink, refresh, cancel, unlink, refetchStatus, … }` | `directory.bankid.*` — no scope (JWT-gated self-service) |
 | **FILESTORE** (`ctx.filestore`) | `usePdfExport({ spaceType, folderId })` (optional: spaceType, folderId) | `{ openPdf, opening, canOpenPdf, exportToPdf, exporting, error, lastExported }` | `ctx.filestore.files.renderPdf` + `ctx.device.pdfViewer`, `ctx.filestore.files.exportPdf` — `files.write:*`. `openPdf(html, { fileName? })` renders the HTML to a PDF server-side and OPENS it (web: PDF tab; native: print / share sheet) without saving. `exportToPdf(html, { fileName?, folderId? })` renders it and saves it as a file (`application/pdf`). Same server-side renderer on web + native. |
 | **PAYMENTS** (`ctx.payments`) | `usePayments()` | `{ requestPayment, getPayment }` | `ctx.payments.*` — `payments.charge:appUser`. Rejects with `PaymentError { code, message, retryable }`; when `retryable` is `false` show `message` and drop the retry. Charges are accepted ONLY in the currency the workspace sells in — omit `currency` and the platform applies it (a disagreeing literal is a publish-blocking `payment-currency` finding). |
@@ -77,7 +77,59 @@ See the design reference for the full architecture: [`docs/architecture/widget-m
 
 ## Status
 
-`v0.193.0` — pre-publish. The package surface (types, function names, export paths) is the v1 contract; runtime behaviour for some hooks is stubbed (each hook documents what's wired and what isn't). It is **not yet published to npm**.
+`v0.195.0` — pre-publish. The package surface (types, function names, export paths) is the v1 contract; runtime behaviour for some hooks is stubbed (each hook documents what's wired and what isn't). It is **not yet published to npm**.
+
+### What's new in 0.195.0 (contract 1.156.0)
+
+**An admin can correct a member's name or email — `useUsers().update(userId, { name, email })`.** Send either key or both; it resolves `{ id, name, email }`. Call `refetch()` afterwards to refresh the list.
+
+```jsx
+import { useUsers } from "@colixsystems/widget-sdk";
+
+// Manifest: requestedScopes: ["users.read:*", "users.write:*"]
+function ChangeMemberEmail({ user }) {
+  const { update, refetch } = useUsers();
+  const save = async (email) => {
+    try {
+      await update(user.id, { email });
+      await refetch();
+    } catch (err) {
+      if (err.reason === "EMAIL_TAKEN") { /* mark the email field */ }
+      // err.message is a sentence written for the person reading it.
+    }
+  };
+  return null;
+}
+```
+
+- **It needs `users.write:*`**, the same scope as `invite` and `deactivate`, plus the workspace's `users.write` capability for the signed-in person. **That scope now also covers changing a member's name and sign-in email**, which is a sensitive power: request it only for a surface meant for the people who administer the app. The linter asks for the scope when a source that calls `useUsers(` also calls `.update(`. If that `.update(` belongs to something else, end the line with `// @appstudio-skip-scope-check`.
+- **An email change is announced to the user at their previous address**, so a change they did not expect never goes unnoticed. You do not send that message yourself.
+- **Refusals name their reason.** `DirectoryError` gains `reason`, the host's specific refusal code, or `null` when it gave none. `code` stays the broad category.
+
+| `err.code` | `err.reason` | Meaning |
+| --- | --- | --- |
+| `VALIDATION` | `INVALID_UPDATE` | Neither `name` nor `email` was sent |
+| `VALIDATION` | `INVALID_NAME` / `INVALID_EMAIL` | The value is empty, too long or not an address |
+| `VALIDATION` | `EMAIL_TAKEN` | The address is not available |
+| `VALIDATION` | `EMAIL_RESERVED` | A reserved address |
+| `VALIDATION` | `SCIM_MANAGED_NAME` / `SCIM_MANAGED_EMAIL` | The profile is synced from an identity provider; change it there |
+| `VALIDATION` | `SSO_LINKED_EMAIL` | The user signs in through an identity provider; change the email there |
+| `VALIDATION` | `SERVICE_ACCOUNT_PROTECTED` | A service account's email cannot be changed |
+| `VALIDATION` | `SEED_USER_PROTECTED` / `REVIEW_USER_PROTECTED` | The app's preview or store-review account: its email address cannot be changed |
+| `VALIDATION` | `OWN_EMAIL_CHANGE_REFUSED` | The signed-in user cannot change their own email here; they use their account screen |
+| `NOT_FOUND` | | No such user in this workspace |
+| `FORBIDDEN` | | The signed-in person may not edit users |
+| `INTERNAL` (`err.status === 429`) | | Too many email changes in a short time; `err.retryable` is `true` |
+
+Every refusal from `EMAIL_TAKEN` down to `OWN_EMAIL_CHANGE_REFUSED`, except the `SCIM_MANAGED_*` pair, concerns the email only: a rename sent as `{ name }` alone still succeeds. `useUsers()` lists service accounts, so expect `SERVICE_ACCOUNT_PROTECTED`; better, do not offer an email field on a row whose `role` is `INTEGRATION`.
+
+Email changes are rate-limited per caller. The call is never retried automatically, so a 429 reaches you at once: ask the person to try again later rather than looping.
+
+`reason` is set on every `DirectoryError` the host explains, so `sendPasswordReset()` refusals read `err.reason === "USER_INACTIVE"` or `"NO_PASSWORD_CREDENTIAL"`. Additive: a host that does not offer `update` yet rejects the call with an `INTERNAL` `DirectoryError`.
+
+### What's new in 0.194.0 (contract 1.155.0)
+
+**Send-later invitations are withdrawn.** 0.183.0 let `useUsers().invite()` take `send_invitation: false` to store an invitation without emailing it. That argument, the `not_sent` invite status and the `sent_at` field are removed: `invite()` emails the invitation at once, as it did before, and `useInvites().resend(inviteId)` re-sends a pending one. A widget that wants to line people up first keeps its own list and calls `invite()` when it is ready.
 
 ### What's new in 0.193.0 (contract 1.154.0)
 
@@ -250,24 +302,7 @@ An installed widget is not rebuilt or republished for this. The web Player hands
 
 ### What's new in 0.183.0 (contract 1.144.0)
 
-**A widget can prepare an invitation now and send it later.** `useUsers().invite()` always emailed the invitation the moment it was created, so a widget could not line people up ahead of a launch day or let a second person check the list first. `invite()` now takes an optional `send_invitation`:
-
-```js
-const { invite } = useUsers();
-const { invites, resend } = useInvites({ status: "not_sent" });
-
-const prepared = await invite({ email: "bo@example.com", name: "Bo", send_invitation: false });
-// prepared.status === "not_sent", prepared.sent_at === null — nobody was emailed.
-
-await resend(prepared.id);   // emails it; the row is now "pending" with a fresh 7-day expiry
-```
-
-- **`send_invitation`** defaults to `true`, so an existing `invite({ email, name, group_ids })` call emails at once exactly as before. `false` stores the invitation and emails nobody. A value that is not a boolean rejects with a `DirectoryError` coded `VALIDATION`.
-- **`not_sent` joins the invite `status` values**, and every invite row carries **`sent_at`** (`null` until the first send). A `not_sent` invitation cannot be accepted yet and its `expires_at` means nothing until it is sent, so show no expiry for it. `useInvites({ status: "not_sent" })` lists just the prepared ones. Where several states apply the first of accepted, revoked, not_sent, expired, pending wins.
-- **`useInvites().resend(inviteId)` is the one call that sends**, whether or not the invitation was sent before. There is no separate `send` method: on a `not_sent` row it is the first send, on a `pending` or `expired` one it sends again, and either way it stamps `sent_at`, restarts the expiry and resolves the row as `pending`. Label the button to match the row — "Send invitation" when `status === "not_sent"`, "Resend" otherwise.
-- **A widget that switches on `status` should handle the new value.** A `not_sent` row falls through an `if (status === "pending")` check, so a list that offers its actions only to pending rows would leave a prepared invitation with no way to send it.
-
-The built-in User Management widget offers the choice on its invite form ("Send the invitation later", off by default) and a "Send invitation" action on each row that has not been sent. No new scope: both calls sit under `users.write:*`, as before.
+Send-later invitations (`send_invitation`, the `not_sent` status, `sent_at`). Withdrawn in 0.194.0.
 
 ### What's new in 0.182.0 (contract 1.143.0)
 
@@ -2249,7 +2284,7 @@ A widget that works but looks unfinished is only half done. `useTheme()` is the
 
 ## Managing app users from a widget
 
-`useUsers()` and `useGroups()` let a widget invite, deactivate, reactivate, and remove members, plus create / delete groups and add / remove their members. Two gates apply: the manifest must declare the scope (the static analyzer + the host's signed `X-Widget-Scopes` header agree), and the calling APP_USER must hold the matching `users.*` / `groups.*` capability (a SystemAcl grant the Studio admin issues via the Roles UI). A widget that declares `users.write:*` but whose caller lacks the grant gets a `DirectoryError` with `code: 'FORBIDDEN'` — surface that as a "you do not have permission" message.
+`useUsers()` and `useGroups()` let a widget invite, deactivate, reactivate, and remove members, change a member's name or sign-in email, plus create / delete groups and add / remove their members. `users.write:*` covers every edit, the name and sign-in email included (the member is told at their previous address when the email changes), so request it only for a surface meant for the people who administer the app. Two gates apply: the manifest must declare the scope (the static analyzer + the host's signed `X-Widget-Scopes` header agree), and the calling APP_USER must hold the matching `users.*` / `groups.*` capability (a SystemAcl grant the Studio admin issues via the Roles UI). A widget that declares `users.write:*` but whose caller lacks the grant gets a `DirectoryError` with `code: 'FORBIDDEN'` — surface that as a "you do not have permission" message.
 
 ```js
 import { Text, View, Pressable, useUsers, useGroups } from "@colixsystems/widget-sdk";
@@ -2294,13 +2329,11 @@ The matching manifest declares the scopes:
 }
 ```
 
-`invite()` emails the invitation at once. Pass `send_invitation: false` to store it without emailing anyone — the row comes back with `status: "not_sent"` and `sent_at: null` — and send it later with `useInvites().resend(inviteId)`.
-
 The host rejects calls whose scope is not declared in the manifest (the SDK linter catches this statically too). Declaring a write scope is also a consent prompt the Studio admin sees at install time — the wider the scope set, the more careful the admin is about granting the install.
 
 ## Listing pending invitations from a widget
 
-`useInvites(query?)` lists the workspace's invites and sends / revokes them:
+`useInvites(query?)` lists the workspace's invites and resends / revokes them:
 
 ```jsx
 import { useInvites, View, Text, Pressable } from '@colixsystems/widget-sdk';
@@ -2315,9 +2348,7 @@ function PendingInvites() {
       {invites.map((i) => (
         <View key={i.id}>
           <Text>{i.email} · {i.status}</Text>
-          <Pressable onPress={() => resend(i.id).catch(() => {})}>
-            <Text>{i.status === 'not_sent' ? 'Send invitation' : 'Resend'}</Text>
-          </Pressable>
+          <Pressable onPress={() => resend(i.id).catch(() => {})}><Text>Resend</Text></Pressable>
           <Pressable onPress={() => revoke(i.id).catch(() => {})}><Text>Revoke</Text></Pressable>
         </View>
       ))}
@@ -2326,16 +2357,9 @@ function PendingInvites() {
 }
 ```
 
-Rows are snake_case: `{ id, app_user_id, email, name, group_ids, status, sent_at,
-expires_at, accepted_at, revoked_at, created_at }`. `status` is one of `pending`,
-`accepted`, `revoked`, `expired` or `not_sent`; trust the server-computed value rather
-than comparing `expires_at` against the device clock.
-
-A `not_sent` row is an invitation created with `send_invitation: false`: nobody has
-been emailed and `sent_at` is `null`. `resend(inviteId)` is the one call that sends
-an invitation, a first send and a repeat send alike — it emails the invitee, stamps
-`sent_at`, restarts the 7-day expiry and resolves the row as `pending`. Pass
-`{ status: 'not_sent' }` to list only the prepared ones.
+Rows are snake_case: `{ id, app_user_id, email, name, group_ids, status, expires_at,
+accepted_at, revoked_at, created_at }`. Trust the server-computed `status` rather than
+comparing `expires_at` against the device clock.
 
 `query` also takes `q` (a case-insensitive substring match on the invite's name or
 email) and `app_user_id`. Each row's `app_user_id` is the id the invitee's user account
@@ -2343,7 +2367,7 @@ will have once they accept. A `USER` column may hold that id before the person h
 joined — it then reads back as `{ id, name, invited: true }`, with no `email` — and
 `useInvites({ app_user_id: value.id, status: 'open', limit: 1 })` returns the invite
 behind it. `status: 'open'` is every invite that is neither accepted nor revoked
-(`pending`, `not_sent` or `expired`); a re-invite keeps the id, so without it earlier invites match too.
+(`pending` or `expired`); a re-invite keeps the id, so without it earlier invites match too.
 
 **The gate is `users.write`, not `users.read`.** A pending invite exposes the email of
 someone who is not a member yet, so the backend gates the entire invite surface —

package/dist/contract.cjs

@@ -1746,12 +1746,11 @@ const HOOKS = [
   // REQ-USERMGMT / REQ-ACL-SYS M3 — AppUser administration. Returns
   // `{ users, loading, error, refetch, invite, deactivate, reactivate, remove }`.
   // Reads need `users.read:*` scope; edit-style mutations (invite /
-  // deactivate / reactivate / sendPasswordReset) additionally need
+  // deactivate / reactivate / sendPasswordReset / update) additionally need
   // `users.write:*`, and the
   // destructive `remove` needs `users.delete:*` (SC-902). The `invite`
-  // call accepts `{ email, name, group_ids?, send_invitation? }` and returns
-  // the resulting AppUserInvite row (the host sends the email, unless
-  // `send_invitation` is false). Mutating users from
+  // call accepts `{ email, name, groupIds? }` and returns the resulting
+  // AppUserInvite row (the email is sent by the host). Mutating users from
   // a widget requires the corresponding SystemAcl capability grant in the
   // tenant (`users.write` for edits, `users.delete` for removal); widgets
   // that only call read methods need only `users.read:*`.
@@ -1761,39 +1760,62 @@ const HOOKS = [
     optionalArgs: ["query"],
     description:
       "AppUser administration via the injected directory-client at " +
-      "ctx.directory.users.{list,get,invite,deactivate,reactivate,sendPasswordReset}. " +
+      "ctx.directory.users.{list,get,invite,deactivate,reactivate,sendPasswordReset,update}. " +
       "Returns { users, loading, error, refetch, invite, deactivate, " +
-      "reactivate, remove, sendPasswordReset }. " +
+      "reactivate, remove, sendPasswordReset, update }. " +
       "list returns the { data, meta } envelope verbatim — the hook unwraps " +
       "res.data; rows are snake_case (is_active, …). Reads need users.read:* " +
       "scope; edit-style mutations (invite/deactivate/reactivate/" +
-      "sendPasswordReset) need users.write:*, and the destructive remove() " +
+      "sendPasswordReset/update) need users.write:*, and the destructive remove() " +
       "additionally needs users.delete:* (SC-902). The `invite` call accepts " +
-      "{ email, name, group_ids?, send_invitation? } and returns the resulting " +
-      "AppUserInvite row { id, email, name, expires_at, sent_at, status }. " +
-      "The host emails the invitation at once unless send_invitation is " +
-      "false: then nothing is emailed, the row comes back with sent_at null " +
-      "and status 'not_sent', and useInvites().resend(inviteId) sends it " +
-      "later. A send_invitation that is not a boolean rejects with " +
-      "DirectoryError code VALIDATION. sendPasswordReset(userId) mails the " +
+      "{ email, name, group_ids? } and returns the resulting AppUserInvite row " +
+      "(the email is sent by the host). sendPasswordReset(userId) mails the " +
       "standard self-serve reset link to that user's own registered address " +
       "and resolves { sent, email_masked } — never the token or the link, so " +
       "it cannot be used to sign in as them. It rejects with a DirectoryError " +
-      "coded USER_INACTIVE (deactivated) or NO_PASSWORD_CREDENTIAL (an " +
-      "INTEGRATION service account); surface those as an explanation rather " +
-      "than a generic failure.",
+      "whose reason is USER_INACTIVE (deactivated) or NO_PASSWORD_CREDENTIAL " +
+      "(an INTEGRATION service account); surface those as an explanation " +
+      "rather than a generic failure. update(userId, { name?, email? }) " +
+      "changes a user's name, email, or both (at least one key) and resolves " +
+      "{ id, name, email }; refetch() to refresh the list. An email change " +
+      "notifies the user at their previous address. users.write:* therefore " +
+      "lets a widget change a member's name and sign-in email: request it " +
+      "only for a surface meant for the people who administer the app. It " +
+      "rejects with a DirectoryError; code is the broad category and reason " +
+      "the specific refusal. code VALIDATION comes with reason " +
+      "INVALID_UPDATE (neither key), INVALID_NAME, INVALID_EMAIL, " +
+      "EMAIL_TAKEN (the address is not available), EMAIL_RESERVED (a " +
+      "reserved address), SCIM_MANAGED_NAME / SCIM_MANAGED_EMAIL (the " +
+      "profile is synced from an identity provider, so it is changed there), " +
+      "SSO_LINKED_EMAIL (the user signs in through an identity provider, so " +
+      "the email is changed there), SERVICE_ACCOUNT_PROTECTED (a service " +
+      "account's email cannot be changed), SEED_USER_PROTECTED / " +
+      "REVIEW_USER_PROTECTED (the app's preview or store-review account: " +
+      "its email address cannot be changed) or OWN_EMAIL_CHANGE_REFUSED " +
+      "(the signed-in user cannot change their own email here; they use " +
+      "their account screen). Every refusal from EMAIL_TAKEN on, except " +
+      "the SCIM_MANAGED pair, concerns the email only: a rename sent as " +
+      "{ name } alone still succeeds. code NOT_FOUND is an unknown user; " +
+      "code FORBIDDEN a caller without the users.write capability. Email " +
+      "changes are rate-limited per caller: an HTTP 429 arrives as code " +
+      "INTERNAL with status 429 and retryable true, and is never retried " +
+      "automatically, so ask the person to try again later. " +
+      "DirectoryError.reason is the host's specific refusal code, or null " +
+      "when it gave none; branch on it, and show error.message to the person.",
     returnShape: {
       users: "Array<{ id, name, email?, role, is_active }>  // snake_case rows; unwrapped from { data, meta }",
       loading: "boolean",
-      error: "DirectoryError | null  // { code, message, retryable }",
+      error: "DirectoryError | null  // { code, reason, message, retryable }",
       refetch: "() => Promise<void>",
       invite:
-        "({ email, name, group_ids?, send_invitation? }) => Promise<Invite>  // send_invitation: false stores it unsent (status 'not_sent'); rejects with DirectoryError",
+        "({ email, name, group_ids? }) => Promise<Invite>  // rejects with DirectoryError",
       deactivate: "(userId) => Promise<User>  // rejects with DirectoryError",
       reactivate: "(userId) => Promise<User>  // rejects with DirectoryError",
       remove: "(userId) => Promise<void>  // rejects with DirectoryError",
       sendPasswordReset:
         "(userId) => Promise<{ sent, email_masked }>  // rejects with DirectoryError",
+      update:
+        "(userId, { name?, email? }) => Promise<{ id, name, email }>  // at least one key; an email change notifies the user at their previous address; rejects with DirectoryError (reason EMAIL_TAKEN, SERVICE_ACCOUNT_PROTECTED, …; status 429 when rate-limited)",
     },
     requiredContextSlice: ["directory.users"],
     scopes: ["users.read:*"],
@@ -1833,8 +1855,7 @@ const HOOKS = [
   // sc-5097 — pending AppUser invite administration. Returns
   // `{ invites, loading, error, refetch, resend, revoke }`. Reads need
   // `invites.read:*`; resend/revoke need `invites.write:*` plus the
-  // caller's `users.write` SystemAcl capability. sc-9714: `resend` is also
-  // the first send of a `not_sent` invite — there is no separate `send`.
+  // caller's `users.write` SystemAcl capability.
   {
     name: "useInvites",
     signature: "useInvites(query)",
@@ -1844,23 +1865,13 @@ const HOOKS = [
       "directory-client at ctx.directory.invites.{list,resend,revoke}. " +
       "Returns { invites, loading, error, refetch, resend, revoke }. list " +
       "returns the { data, meta } envelope verbatim — the hook unwraps " +
-      "res.data; rows are snake_case (email, status, sent_at, expires_at, …) " +
-      "and status is the server-computed pending/accepted/revoked/expired/" +
-      "not_sent value. not_sent is an invitation created with " +
-      "send_invitation: false that has not been emailed yet: its sent_at is " +
-      "null, it cannot be accepted until it is sent, and its expires_at " +
-      "means nothing yet, so show no expiry for it. resend(inviteId) is the " +
-      "ONE call that sends an invitation — the first send of a not_sent one " +
-      "and a repeat send of a sent one alike: it emails the invitee, stamps " +
-      "sent_at, restarts the 7-day expiry and resolves the row with status " +
-      "'pending'. There is no separate send method; label the button " +
-      "'Send invitation' on a not_sent row and 'Resend' on a pending one. " +
-      "query is { status?, q?, app_user_id?, limit?, offset? } passed " +
+      "res.data; rows are snake_case (email, status, expires_at, …) and " +
+      "status is the server-computed pending/accepted/revoked/expired " +
+      "value. query is { status?, q?, app_user_id?, limit?, offset? } passed " +
       "verbatim; the endpoint defaults to status 'all', so pass " +
-      "{ status: 'pending' } for the usual outstanding-invite list and " +
-      "{ status: 'not_sent' } for the prepared ones; " +
-      "status 'open' is every invite neither accepted nor revoked (pending, " +
-      "not_sent or expired). q is a " +
+      "{ status: 'pending' } for the usual outstanding-invite list; " +
+      "status 'open' is every invite neither accepted nor revoked (pending " +
+      "or expired). q is a " +
       "case-insensitive substring match on the invite's name or email. " +
       "Each row's app_user_id is the id the invitee's user account will " +
       "have once they accept; a USER column may already hold it, and " +
@@ -1877,12 +1888,12 @@ const HOOKS = [
       "refetch on success.",
     returnShape: {
       invites:
-        "Array<{ id, app_user_id, email, name, group_ids, status, sent_at, expires_at, accepted_at, revoked_at, created_at }>  // snake_case rows; status is pending | accepted | revoked | expired | not_sent; unwrapped from { data, meta }",
+        "Array<{ id, app_user_id, email, name, group_ids, status, expires_at, accepted_at, revoked_at, created_at }>  // snake_case rows; unwrapped from { data, meta }",
       loading: "boolean",
       error: "DirectoryError | null  // { code, message, retryable }",
       refetch: "() => Promise<void>",
       resend:
-        "(inviteId) => Promise<Invite>  // sends it (first send of a not_sent invite too); refetches; rejects with DirectoryError",
+        "(inviteId) => Promise<Invite>  // refetches; rejects with DirectoryError",
       revoke:
         "(inviteId) => Promise<void>  // refetches; rejects with DirectoryError",
     },
@@ -3049,7 +3060,7 @@ const WIDGET_CONTEXT_SHAPE = {
       "groups: { list(query?) -> Promise<{ data, meta }>, create(body), remove(id), addMember(groupId, userId), removeMember(groupId, userId), listMine() }, " +
       "invites: { list(), revoke(id), resend(id) }, " +
       "bankid: { status() -> { linked, available }, startLink() -> { order_ref, qr, ... }, collect(orderRef), cancel(orderRef), unlink() } }. " +
-      "users backs useDirectory() + useUsers(); groups backs useGroups(); invites backs useInvites() (list/resend/revoke invites — resend also sends one created with send_invitation: false — gated by users.write:* + the users.write capability); bankid backs useBankIdLink() (REQ-BANKID-AUTH — self-service account linking, JWT-gated, no widget scope). List methods return the { data, meta } envelope verbatim (hooks unwrap res.data); rows/bodies are snake_case. Reads gated by directory.read:users / users.read:* / groups.read:*; mutations by users.write:* / groups.write:* (destructive user removal by users.delete:*).",
+      "users backs useDirectory() + useUsers(); groups backs useGroups(); invites backs useInvites() (list/resend/revoke pending invites, gated by users.write:* + the users.write capability); bankid backs useBankIdLink() (REQ-BANKID-AUTH — self-service account linking, JWT-gated, no widget scope). List methods return the { data, meta } envelope verbatim (hooks unwrap res.data); rows/bodies are snake_case. Reads gated by directory.read:users / users.read:* / groups.read:*; mutations by users.write:* / groups.write:* (destructive user removal by users.delete:*).",
     required: true,
     fields: { users: "object", groups: "object", invites: "object", bankid: "object" },
   },
@@ -5081,7 +5092,14 @@ const CONTRACT = deepFreeze({
   //    `scope: { kind: "granted" }` (the rows the signed-in user reads through
   //    a user or group grant) and the `onAccessGained` / `onAccessLost`
   //    handlers that report rows entering and leaving that set.
-  version: "1.154.0",
+  // 1.155.0: narrowing (sc-10566) — withdraws 1.144.0: `useUsers().invite`
+  //    takes no `send_invitation` and always emails, invite rows carry no
+  //    `sent_at`, and `not_sent` is no longer a status.
+  // 1.156.0: additive (sc-10429) — `useUsers()` gains
+  //    `update(userId, { name?, email? })`, gated on `users.write:*`; the
+  //    linter requires that scope for a `.update(` call beside `useUsers(`.
+  //    `DirectoryError` gains `reason`, the host's specific refusal code.
+  version: "1.156.0",
   sharedTranslationKeys: SHARED_TRANSLATION_KEYS,
   hooks: HOOKS,
   primitives: PRIMITIVES,

package/dist/contract.js

@@ -1746,12 +1746,11 @@ const HOOKS = [
   // REQ-USERMGMT / REQ-ACL-SYS M3 — AppUser administration. Returns
   // `{ users, loading, error, refetch, invite, deactivate, reactivate, remove }`.
   // Reads need `users.read:*` scope; edit-style mutations (invite /
-  // deactivate / reactivate / sendPasswordReset) additionally need
+  // deactivate / reactivate / sendPasswordReset / update) additionally need
   // `users.write:*`, and the
   // destructive `remove` needs `users.delete:*` (SC-902). The `invite`
-  // call accepts `{ email, name, group_ids?, send_invitation? }` and returns
-  // the resulting AppUserInvite row (the host sends the email, unless
-  // `send_invitation` is false). Mutating users from
+  // call accepts `{ email, name, groupIds? }` and returns the resulting
+  // AppUserInvite row (the email is sent by the host). Mutating users from
   // a widget requires the corresponding SystemAcl capability grant in the
   // tenant (`users.write` for edits, `users.delete` for removal); widgets
   // that only call read methods need only `users.read:*`.
@@ -1761,39 +1760,62 @@ const HOOKS = [
     optionalArgs: ["query"],
     description:
       "AppUser administration via the injected directory-client at " +
-      "ctx.directory.users.{list,get,invite,deactivate,reactivate,sendPasswordReset}. " +
+      "ctx.directory.users.{list,get,invite,deactivate,reactivate,sendPasswordReset,update}. " +
       "Returns { users, loading, error, refetch, invite, deactivate, " +
-      "reactivate, remove, sendPasswordReset }. " +
+      "reactivate, remove, sendPasswordReset, update }. " +
       "list returns the { data, meta } envelope verbatim — the hook unwraps " +
       "res.data; rows are snake_case (is_active, …). Reads need users.read:* " +
       "scope; edit-style mutations (invite/deactivate/reactivate/" +
-      "sendPasswordReset) need users.write:*, and the destructive remove() " +
+      "sendPasswordReset/update) need users.write:*, and the destructive remove() " +
       "additionally needs users.delete:* (SC-902). The `invite` call accepts " +
-      "{ email, name, group_ids?, send_invitation? } and returns the resulting " +
-      "AppUserInvite row { id, email, name, expires_at, sent_at, status }. " +
-      "The host emails the invitation at once unless send_invitation is " +
-      "false: then nothing is emailed, the row comes back with sent_at null " +
-      "and status 'not_sent', and useInvites().resend(inviteId) sends it " +
-      "later. A send_invitation that is not a boolean rejects with " +
-      "DirectoryError code VALIDATION. sendPasswordReset(userId) mails the " +
+      "{ email, name, group_ids? } and returns the resulting AppUserInvite row " +
+      "(the email is sent by the host). sendPasswordReset(userId) mails the " +
       "standard self-serve reset link to that user's own registered address " +
       "and resolves { sent, email_masked } — never the token or the link, so " +
       "it cannot be used to sign in as them. It rejects with a DirectoryError " +
-      "coded USER_INACTIVE (deactivated) or NO_PASSWORD_CREDENTIAL (an " +
-      "INTEGRATION service account); surface those as an explanation rather " +
-      "than a generic failure.",
+      "whose reason is USER_INACTIVE (deactivated) or NO_PASSWORD_CREDENTIAL " +
+      "(an INTEGRATION service account); surface those as an explanation " +
+      "rather than a generic failure. update(userId, { name?, email? }) " +
+      "changes a user's name, email, or both (at least one key) and resolves " +
+      "{ id, name, email }; refetch() to refresh the list. An email change " +
+      "notifies the user at their previous address. users.write:* therefore " +
+      "lets a widget change a member's name and sign-in email: request it " +
+      "only for a surface meant for the people who administer the app. It " +
+      "rejects with a DirectoryError; code is the broad category and reason " +
+      "the specific refusal. code VALIDATION comes with reason " +
+      "INVALID_UPDATE (neither key), INVALID_NAME, INVALID_EMAIL, " +
+      "EMAIL_TAKEN (the address is not available), EMAIL_RESERVED (a " +
+      "reserved address), SCIM_MANAGED_NAME / SCIM_MANAGED_EMAIL (the " +
+      "profile is synced from an identity provider, so it is changed there), " +
+      "SSO_LINKED_EMAIL (the user signs in through an identity provider, so " +
+      "the email is changed there), SERVICE_ACCOUNT_PROTECTED (a service " +
+      "account's email cannot be changed), SEED_USER_PROTECTED / " +
+      "REVIEW_USER_PROTECTED (the app's preview or store-review account: " +
+      "its email address cannot be changed) or OWN_EMAIL_CHANGE_REFUSED " +
+      "(the signed-in user cannot change their own email here; they use " +
+      "their account screen). Every refusal from EMAIL_TAKEN on, except " +
+      "the SCIM_MANAGED pair, concerns the email only: a rename sent as " +
+      "{ name } alone still succeeds. code NOT_FOUND is an unknown user; " +
+      "code FORBIDDEN a caller without the users.write capability. Email " +
+      "changes are rate-limited per caller: an HTTP 429 arrives as code " +
+      "INTERNAL with status 429 and retryable true, and is never retried " +
+      "automatically, so ask the person to try again later. " +
+      "DirectoryError.reason is the host's specific refusal code, or null " +
+      "when it gave none; branch on it, and show error.message to the person.",
     returnShape: {
       users: "Array<{ id, name, email?, role, is_active }>  // snake_case rows; unwrapped from { data, meta }",
       loading: "boolean",
-      error: "DirectoryError | null  // { code, message, retryable }",
+      error: "DirectoryError | null  // { code, reason, message, retryable }",
       refetch: "() => Promise<void>",
       invite:
-        "({ email, name, group_ids?, send_invitation? }) => Promise<Invite>  // send_invitation: false stores it unsent (status 'not_sent'); rejects with DirectoryError",
+        "({ email, name, group_ids? }) => Promise<Invite>  // rejects with DirectoryError",
       deactivate: "(userId) => Promise<User>  // rejects with DirectoryError",
       reactivate: "(userId) => Promise<User>  // rejects with DirectoryError",
       remove: "(userId) => Promise<void>  // rejects with DirectoryError",
       sendPasswordReset:
         "(userId) => Promise<{ sent, email_masked }>  // rejects with DirectoryError",
+      update:
+        "(userId, { name?, email? }) => Promise<{ id, name, email }>  // at least one key; an email change notifies the user at their previous address; rejects with DirectoryError (reason EMAIL_TAKEN, SERVICE_ACCOUNT_PROTECTED, …; status 429 when rate-limited)",
     },
     requiredContextSlice: ["directory.users"],
     scopes: ["users.read:*"],
@@ -1833,8 +1855,7 @@ const HOOKS = [
   // sc-5097 — pending AppUser invite administration. Returns
   // `{ invites, loading, error, refetch, resend, revoke }`. Reads need
   // `invites.read:*`; resend/revoke need `invites.write:*` plus the
-  // caller's `users.write` SystemAcl capability. sc-9714: `resend` is also
-  // the first send of a `not_sent` invite — there is no separate `send`.
+  // caller's `users.write` SystemAcl capability.
   {
     name: "useInvites",
     signature: "useInvites(query)",
@@ -1844,23 +1865,13 @@ const HOOKS = [
       "directory-client at ctx.directory.invites.{list,resend,revoke}. " +
       "Returns { invites, loading, error, refetch, resend, revoke }. list " +
       "returns the { data, meta } envelope verbatim — the hook unwraps " +
-      "res.data; rows are snake_case (email, status, sent_at, expires_at, …) " +
-      "and status is the server-computed pending/accepted/revoked/expired/" +
-      "not_sent value. not_sent is an invitation created with " +
-      "send_invitation: false that has not been emailed yet: its sent_at is " +
-      "null, it cannot be accepted until it is sent, and its expires_at " +
-      "means nothing yet, so show no expiry for it. resend(inviteId) is the " +
-      "ONE call that sends an invitation — the first send of a not_sent one " +
-      "and a repeat send of a sent one alike: it emails the invitee, stamps " +
-      "sent_at, restarts the 7-day expiry and resolves the row with status " +
-      "'pending'. There is no separate send method; label the button " +
-      "'Send invitation' on a not_sent row and 'Resend' on a pending one. " +
-      "query is { status?, q?, app_user_id?, limit?, offset? } passed " +
+      "res.data; rows are snake_case (email, status, expires_at, …) and " +
+      "status is the server-computed pending/accepted/revoked/expired " +
+      "value. query is { status?, q?, app_user_id?, limit?, offset? } passed " +
       "verbatim; the endpoint defaults to status 'all', so pass " +
-      "{ status: 'pending' } for the usual outstanding-invite list and " +
-      "{ status: 'not_sent' } for the prepared ones; " +
-      "status 'open' is every invite neither accepted nor revoked (pending, " +
-      "not_sent or expired). q is a " +
+      "{ status: 'pending' } for the usual outstanding-invite list; " +
+      "status 'open' is every invite neither accepted nor revoked (pending " +
+      "or expired). q is a " +
       "case-insensitive substring match on the invite's name or email. " +
       "Each row's app_user_id is the id the invitee's user account will " +
       "have once they accept; a USER column may already hold it, and " +
@@ -1877,12 +1888,12 @@ const HOOKS = [
       "refetch on success.",
     returnShape: {
       invites:
-        "Array<{ id, app_user_id, email, name, group_ids, status, sent_at, expires_at, accepted_at, revoked_at, created_at }>  // snake_case rows; status is pending | accepted | revoked | expired | not_sent; unwrapped from { data, meta }",
+        "Array<{ id, app_user_id, email, name, group_ids, status, expires_at, accepted_at, revoked_at, created_at }>  // snake_case rows; unwrapped from { data, meta }",
       loading: "boolean",
       error: "DirectoryError | null  // { code, message, retryable }",
       refetch: "() => Promise<void>",
       resend:
-        "(inviteId) => Promise<Invite>  // sends it (first send of a not_sent invite too); refetches; rejects with DirectoryError",
+        "(inviteId) => Promise<Invite>  // refetches; rejects with DirectoryError",
       revoke:
         "(inviteId) => Promise<void>  // refetches; rejects with DirectoryError",
     },
@@ -3045,7 +3056,7 @@ const WIDGET_CONTEXT_SHAPE = {
       "groups: { list(query?) -> Promise<{ data, meta }>, create(body), remove(id), addMember(groupId, userId), removeMember(groupId, userId), listMine() }, " +
       "invites: { list(), revoke(id), resend(id) }, " +
       "bankid: { status() -> { linked, available }, startLink() -> { order_ref, qr, ... }, collect(orderRef), cancel(orderRef), unlink() } }. " +
-      "users backs useDirectory() + useUsers(); groups backs useGroups(); invites backs useInvites() (list/resend/revoke invites — resend also sends one created with send_invitation: false — gated by users.write:* + the users.write capability); bankid backs useBankIdLink() (REQ-BANKID-AUTH — self-service account linking, JWT-gated, no widget scope). List methods return the { data, meta } envelope verbatim (hooks unwrap res.data); rows/bodies are snake_case. Reads gated by directory.read:users / users.read:* / groups.read:*; mutations by users.write:* / groups.write:* (destructive user removal by users.delete:*).",
+      "users backs useDirectory() + useUsers(); groups backs useGroups(); invites backs useInvites() (list/resend/revoke pending invites, gated by users.write:* + the users.write capability); bankid backs useBankIdLink() (REQ-BANKID-AUTH — self-service account linking, JWT-gated, no widget scope). List methods return the { data, meta } envelope verbatim (hooks unwrap res.data); rows/bodies are snake_case. Reads gated by directory.read:users / users.read:* / groups.read:*; mutations by users.write:* / groups.write:* (destructive user removal by users.delete:*).",
     required: true,
     fields: { users: "object", groups: "object", invites: "object", bankid: "object" },
   },
@@ -5077,7 +5088,14 @@ const CONTRACT = deepFreeze({
   //    `scope: { kind: "granted" }` (the rows the signed-in user reads through
   //    a user or group grant) and the `onAccessGained` / `onAccessLost`
   //    handlers that report rows entering and leaving that set.
-  version: "1.154.0",
+  // 1.155.0: narrowing (sc-10566) — withdraws 1.144.0: `useUsers().invite`
+  //    takes no `send_invitation` and always emails, invite rows carry no
+  //    `sent_at`, and `not_sent` is no longer a status.
+  // 1.156.0: additive (sc-10429) — `useUsers()` gains
+  //    `update(userId, { name?, email? })`, gated on `users.write:*`; the
+  //    linter requires that scope for a `.update(` call beside `useUsers(`.
+  //    `DirectoryError` gains `reason`, the host's specific refusal code.
+  version: "1.156.0",
   sharedTranslationKeys: SHARED_TRANSLATION_KEYS,
   hooks: HOOKS,
   primitives: PRIMITIVES,

package/dist/hooks.js

@@ -5394,6 +5394,8 @@ export function useFolderPermissions(folderId, options = {}) {
  *   - "INVITE_ONLY" — 409 from accept-invite-style flows where the tenant
  *                     is invite-only and the email is not on the list.
  *   - "INTERNAL"    — anything else (network, 5xx).
+ *
+ * `reason` is the host's own refusal code ("EMAIL_TAKEN", …) or null.
  */
 // sc-4986 — the directory refusals retrying the same call can never clear.
 const NON_RETRYABLE_DIRECTORY_CODES = new Set([
@@ -5415,6 +5417,10 @@ export class DirectoryError extends Error {
       opts && opts.retryable !== undefined
         ? Boolean(opts.retryable)
         : !NON_RETRYABLE_DIRECTORY_CODES.has(code);
+    this.reason =
+      opts && typeof opts.reason === "string" && opts.reason
+        ? opts.reason
+        : null;
     if (opts && opts.cause) this.cause = opts.cause;
   }
 }
@@ -5440,7 +5446,12 @@ function toDirectoryError(err) {
       (err && typeof err.message === "string"
         ? err.message
         : "Directory call failed"),
-    { cause: err, status, retryable: isRetryableDomainStatus(status) },
+    {
+      cause: err,
+      status,
+      retryable: isRetryableDomainStatus(status),
+      reason: envelopeCode,
+    },
   );
 }
 
@@ -5534,12 +5545,12 @@ export function useDirectory(query) {
  * REQ-USERMGMT / REQ-ACL-SYS M3 — AppUser administration hook.
  *
  * Returns `{ users, loading, error, refetch, invite, deactivate,
- * reactivate, remove }`. Reads through the injected
+ * reactivate, remove, sendPasswordReset, update }`. Reads through the injected
  * `@colixsystems/directory-client` at `ctx.directory.users.{list, get,
- * invite, deactivate, reactivate}` — `list` resolves to the `{ data, meta }`
+ * invite, deactivate, reactivate, sendPasswordReset, update}` — `list` resolves to the `{ data, meta }`
  * envelope VERBATIM, so we unwrap `res.data` (default `[]`). User rows are
  * snake_case (`id`, `name`, `email`, `role`, `is_active`, …) and bodies
- * (e.g. `{ email, name, group_ids?, send_invitation? }`) pass through verbatim. `query` is an
+ * (e.g. `{ email, name, group_ids? }`) pass through verbatim. `query` is an
  * optional `{ q?, role?, is_active?, group_id?, limit?, offset? }`; `group_id`
  * (the `id` of a `useGroups()` row) narrows the list to that group's members.
  * The list refetches whenever `JSON.stringify(query)` changes; the imperative methods
@@ -5637,7 +5648,7 @@ export function useUsers(query) {
   // sc-5335: mail the self-serve reset link to a user who has locked
   // themselves out. Resolves `{ sent, email_masked }`; the host never returns
   // the token, so this cannot be used to sign in as that user. Rejects with a
-  // DirectoryError carrying `code` USER_INACTIVE or NO_PASSWORD_CREDENTIAL
+  // DirectoryError carrying `reason` USER_INACTIVE or NO_PASSWORD_CREDENTIAL
   // when the target cannot receive one.
   const sendPasswordReset = useCallback(async (userId) => {
     if (typeof usersRef.current.sendPasswordReset !== "function") {
@@ -5653,6 +5664,19 @@ export function useUsers(query) {
       throw toDirectoryError(err);
     }
   }, []);
+  // An email change notifies the user at their previous address.
+  const update = useCallback(async (userId, changes) => {
+    if (typeof usersRef.current.update !== "function") {
+      throw toDirectoryError(
+        new Error("useUsers: this host's directory client predates update"),
+      );
+    }
+    try {
+      return await usersRef.current.update(userId, changes);
+    } catch (err) {
+      throw toDirectoryError(err);
+    }
+  }, []);
 
   return {
     users,
@@ -5664,6 +5688,7 @@ export function useUsers(query) {
     reactivate,
     remove,
     sendPasswordReset,
+    update,
   };
 }
 
@@ -5776,20 +5801,15 @@ export function useGroups(query) {
  * `{ data, meta }` envelope VERBATIM, so we unwrap `res.data` (default `[]`).
  *
  * Rows are snake_case exactly as the backend projects them: `{ id, tenant_id,
- * email, name, group_ids, status, sent_at, expires_at, accepted_at,
- * revoked_at, created_at, invited_by_studio_user_id }`. `status` is the
- * server-computed lifecycle value (`"pending" | "accepted" | "revoked" |
- * "expired" | "not_sent"`) — prefer it over re-deriving expiry on the client,
- * whose clock may disagree.
- *
- * `not_sent` is an invite created with `send_invitation: false`: `sent_at` is
- * null and nothing was emailed. `resend(inviteId)` is the one call that sends
- * — a first send and a repeat send alike — and resolves the row as `pending`.
+ * email, name, group_ids, status, expires_at, accepted_at, revoked_at,
+ * created_at, invited_by_studio_user_id }`. `status` is the server-computed
+ * lifecycle value (`"pending" | "accepted" | "revoked" | "expired"`) — prefer
+ * it over re-deriving expiry on the client, whose clock may disagree.
  *
  * `query` is an optional `{ status?, limit?, offset? }` passed through
  * verbatim; `status` accepts `"pending" | "accepted" | "revoked" | "expired" |
- * "not_sent" | "all"` and the endpoint defaults to `"all"`, so pass
- * `{ status: "pending" }` for the usual "who hasn't accepted yet" list.
+ * "all"` and the endpoint defaults to `"all"`, so pass `{ status: "pending" }`
+ * for the usual "who hasn't accepted yet" list.
  *
  * The WHOLE invite surface — list included — is gated on the `users.write`
  * capability plus a signed `users.write:*` scope: a pending invite exposes
@@ -5856,8 +5876,7 @@ export function useInvites(query) {
   }, [doFetch]);
 
   // Both mutations re-list on success: revoking drops the row and resending
-  // moves `expires_at` (and a first send's status), so a stale list would
-  // show the operator the old state.
+  // moves `expires_at`, so a stale list would show the operator the old state.
   const resend = useCallback(
     async (inviteId) => {
       try {

package/dist/index.d.ts

@@ -521,6 +521,8 @@ export interface DirectoryClient {
     invite(body: Record<string, unknown>): Promise<unknown>;
     deactivate(userId: string): Promise<unknown>;
     reactivate(userId: string): Promise<unknown>;
+    sendPasswordReset?(userId: string): Promise<unknown>;
+    update?(userId: string, body: Record<string, unknown>): Promise<unknown>;
   };
   groups: {
     list(query?: GroupsQuery): Promise<ListEnvelope>;
@@ -2316,12 +2318,15 @@ export class DirectoryError extends Error {
   status: number | null;
   /** sc-4986 — whether retrying the SAME call could plausibly succeed. */
   retryable: boolean;
+  /** The host's specific refusal code (`"EMAIL_TAKEN"`, …); null when none. */
+  reason: string | null;
   constructor(
     code: DirectoryError["code"],
     message: string,
     opts?: {
       status?: number | null;
       retryable?: boolean;
+      reason?: string | null;
       cause?: unknown;
     },
   );
@@ -2442,25 +2447,13 @@ export interface InviteArgs {
   email: string;
   name?: string;
   group_ids?: string[];
-  /**
-   * Defaults to `true`: the invitation is emailed at once. `false` stores it
-   * without emailing anyone (`status: "not_sent"`); send it later with
-   * `useInvites().resend(inviteId)`.
-   */
-  send_invitation?: boolean;
 }
 
-/**
- * When several apply the first of accepted, revoked, not_sent, expired,
- * pending wins. `not_sent` is an invitation created with
- * `send_invitation: false` that has not been emailed yet.
- */
 export type AppUserInviteStatus =
   | "pending"
   | "accepted"
   | "revoked"
-  | "expired"
-  | "not_sent";
+  | "expired";
 
 export interface AppUserInviteRow {
   id: string;
@@ -2475,9 +2468,7 @@ export interface AppUserInviteRow {
   status: AppUserInviteStatus;
   name?: string;
   group_ids?: string[];
-  /** When the invitation email last left; `null` until it is first sent. */
-  sent_at: string | null;
-  /** Meaningless while `status` is `"not_sent"` — it restarts on the send. */
+  invited_at?: string;
   expires_at?: string;
   accepted_at?: string | null;
   revoked_at?: string | null;
@@ -2486,6 +2477,17 @@ export interface AppUserInviteRow {
   invited_by_studio_user_id?: string | null;
 }
 
+export interface UserProfileChanges {
+  name?: string;
+  email?: string;
+}
+
+export interface AppUserProfile {
+  id: string;
+  name: string | null;
+  email: string | null;
+}
+
 export interface UsersApi {
   users: AppUserRow[];
   loading: boolean;
@@ -2495,11 +2497,29 @@ export interface UsersApi {
   deactivate(userId: string): Promise<AppUserRow>;
   reactivate(userId: string): Promise<AppUserRow>;
   remove(userId: string): Promise<void>;
+  sendPasswordReset(
+    userId: string,
+  ): Promise<{ sent: boolean; email_masked: string }>;
+  /**
+   * Changes a user's name, sign-in email, or both; at least one key is
+   * required. An email change notifies the user at their previous address.
+   * Rejects with a `DirectoryError` whose `reason` names the refusal:
+   * `INVALID_UPDATE`, `INVALID_NAME`, `INVALID_EMAIL`, `EMAIL_TAKEN`,
+   * `EMAIL_RESERVED`, `SCIM_MANAGED_NAME`, `SCIM_MANAGED_EMAIL`,
+   * `SSO_LINKED_EMAIL`, `SERVICE_ACCOUNT_PROTECTED`, `SEED_USER_PROTECTED`,
+   * `REVIEW_USER_PROTECTED`, `OWN_EMAIL_CHANGE_REFUSED`. Email changes are
+   * rate-limited: a 429 rejects with `status: 429`, `code: "INTERNAL"`,
+   * `retryable: true`, and is never retried automatically.
+   */
+  update(
+    userId: string,
+    changes: UserProfileChanges,
+  ): Promise<AppUserProfile>;
 }
 
 /**
  * AppUser administration. Reads through the injected directory-client at
- * `ctx.directory.users.{list,get,invite,deactivate,reactivate}`. Reads
+ * `ctx.directory.users.{list,get,invite,deactivate,reactivate,sendPasswordReset,update}`. Reads
  * require the `users.read:*` scope in the manifest; mutations additionally
  * require `users.write:*`. Widgets that declare the scopes but whose calling
  * APP_USER lacks the corresponding SystemAcl `users.*` capability grant get a
@@ -2546,9 +2566,8 @@ export function useGroups(query?: GroupsQuery): GroupsApi;
 
 export interface InvitesQuery {
   /**
-   * Defaults to "all" server-side; pass "pending" for outstanding invites and
-   * "not_sent" for the ones prepared but not emailed yet.
-   * "open" is "pending", "not_sent" or "expired": neither accepted nor revoked.
+   * Defaults to "all" server-side; pass "pending" for outstanding invites.
+   * "open" is "pending" or "expired": neither accepted nor revoked.
    */
   status?: AppUserInviteStatus | "open" | "all";
   /** Case-insensitive substring match on the invite's name or email. */
@@ -2569,12 +2588,7 @@ export interface InvitesApi {
   loading: boolean;
   error: DirectoryError | null;
   refetch(): Promise<void>;
-  /**
-   * Email the invitation and restart its 7-day expiry. The one call that
-   * sends: the first send of a `not_sent` invitation and a repeat send of a
-   * sent one alike. Resolves the row with `status: "pending"`; refetches on
-   * success.
-   */
+  /** Re-send the invitation email. Refetches on success. */
   resend(inviteId: string): Promise<AppUserInviteRow>;
   /** Cancel a pending invitation. Refetches on success. */
   revoke(inviteId: string): Promise<void>;

package/dist/linter.cjs

@@ -657,6 +657,7 @@ const USER_MUTATION_METHODS = [
   // sc-5335 — mailing a reset link is edit-style, so it rides `users.write`
   // alongside deactivate rather than the destructive `users.delete`.
   "sendPasswordReset",
+  "update",
 ];
 // SC-902 — destructive user removal is gated on the dedicated
 // `users.delete` capability, NOT `users.write`. A widget that calls

package/dist/linter.js

@@ -587,7 +587,7 @@ function _translationApiRules(source) {
 // REQ-USERMGMT / REQ-ACL-SYS M3 — scope-required-for-user-mutation.
 //
 // A widget that calls `useUsers().invite()` / `.deactivate()` /
-// `.reactivate()` / `.sendPasswordReset()` / `.remove()` MUST declare
+// `.reactivate()` / `.sendPasswordReset()` / `.update()` / `.remove()` MUST declare
 // `users.write:*` in its
 // manifest's `requestedScopes`; similarly `useGroups()` mutation methods
 // require `groups.write:*`. The rule is enforced statically so a manifest
@@ -608,6 +608,7 @@ const USER_MUTATION_METHODS = [
   // sc-5335 — mailing a reset link is edit-style, so it rides `users.write`
   // alongside deactivate rather than the destructive `users.delete`.
   "sendPasswordReset",
+  "update",
 ];
 // SC-902 — destructive user removal is gated on the dedicated
 // `users.delete` capability, NOT `users.write`. A widget that calls

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@colixsystems/widget-sdk",
-  "version": "0.193.0",
+  "version": "0.195.0",
   "description": "Common widget interface for AppStudio. Implements WidgetManifest, WidgetContext, property schema, and helper hooks.",
   "homepage": "https://github.com/Colix-AB/AppStudio",
   "type": "module",

package/src/contract.js

@@ -1746,12 +1746,11 @@ const HOOKS = [
   // REQ-USERMGMT / REQ-ACL-SYS M3 — AppUser administration. Returns
   // `{ users, loading, error, refetch, invite, deactivate, reactivate, remove }`.
   // Reads need `users.read:*` scope; edit-style mutations (invite /
-  // deactivate / reactivate / sendPasswordReset) additionally need
+  // deactivate / reactivate / sendPasswordReset / update) additionally need
   // `users.write:*`, and the
   // destructive `remove` needs `users.delete:*` (SC-902). The `invite`
-  // call accepts `{ email, name, group_ids?, send_invitation? }` and returns
-  // the resulting AppUserInvite row (the host sends the email, unless
-  // `send_invitation` is false). Mutating users from
+  // call accepts `{ email, name, groupIds? }` and returns the resulting
+  // AppUserInvite row (the email is sent by the host). Mutating users from
   // a widget requires the corresponding SystemAcl capability grant in the
   // tenant (`users.write` for edits, `users.delete` for removal); widgets
   // that only call read methods need only `users.read:*`.
@@ -1761,39 +1760,62 @@ const HOOKS = [
     optionalArgs: ["query"],
     description:
       "AppUser administration via the injected directory-client at " +
-      "ctx.directory.users.{list,get,invite,deactivate,reactivate,sendPasswordReset}. " +
+      "ctx.directory.users.{list,get,invite,deactivate,reactivate,sendPasswordReset,update}. " +
       "Returns { users, loading, error, refetch, invite, deactivate, " +
-      "reactivate, remove, sendPasswordReset }. " +
+      "reactivate, remove, sendPasswordReset, update }. " +
       "list returns the { data, meta } envelope verbatim — the hook unwraps " +
       "res.data; rows are snake_case (is_active, …). Reads need users.read:* " +
       "scope; edit-style mutations (invite/deactivate/reactivate/" +
-      "sendPasswordReset) need users.write:*, and the destructive remove() " +
+      "sendPasswordReset/update) need users.write:*, and the destructive remove() " +
       "additionally needs users.delete:* (SC-902). The `invite` call accepts " +
-      "{ email, name, group_ids?, send_invitation? } and returns the resulting " +
-      "AppUserInvite row { id, email, name, expires_at, sent_at, status }. " +
-      "The host emails the invitation at once unless send_invitation is " +
-      "false: then nothing is emailed, the row comes back with sent_at null " +
-      "and status 'not_sent', and useInvites().resend(inviteId) sends it " +
-      "later. A send_invitation that is not a boolean rejects with " +
-      "DirectoryError code VALIDATION. sendPasswordReset(userId) mails the " +
+      "{ email, name, group_ids? } and returns the resulting AppUserInvite row " +
+      "(the email is sent by the host). sendPasswordReset(userId) mails the " +
       "standard self-serve reset link to that user's own registered address " +
       "and resolves { sent, email_masked } — never the token or the link, so " +
       "it cannot be used to sign in as them. It rejects with a DirectoryError " +
-      "coded USER_INACTIVE (deactivated) or NO_PASSWORD_CREDENTIAL (an " +
-      "INTEGRATION service account); surface those as an explanation rather " +
-      "than a generic failure.",
+      "whose reason is USER_INACTIVE (deactivated) or NO_PASSWORD_CREDENTIAL " +
+      "(an INTEGRATION service account); surface those as an explanation " +
+      "rather than a generic failure. update(userId, { name?, email? }) " +
+      "changes a user's name, email, or both (at least one key) and resolves " +
+      "{ id, name, email }; refetch() to refresh the list. An email change " +
+      "notifies the user at their previous address. users.write:* therefore " +
+      "lets a widget change a member's name and sign-in email: request it " +
+      "only for a surface meant for the people who administer the app. It " +
+      "rejects with a DirectoryError; code is the broad category and reason " +
+      "the specific refusal. code VALIDATION comes with reason " +
+      "INVALID_UPDATE (neither key), INVALID_NAME, INVALID_EMAIL, " +
+      "EMAIL_TAKEN (the address is not available), EMAIL_RESERVED (a " +
+      "reserved address), SCIM_MANAGED_NAME / SCIM_MANAGED_EMAIL (the " +
+      "profile is synced from an identity provider, so it is changed there), " +
+      "SSO_LINKED_EMAIL (the user signs in through an identity provider, so " +
+      "the email is changed there), SERVICE_ACCOUNT_PROTECTED (a service " +
+      "account's email cannot be changed), SEED_USER_PROTECTED / " +
+      "REVIEW_USER_PROTECTED (the app's preview or store-review account: " +
+      "its email address cannot be changed) or OWN_EMAIL_CHANGE_REFUSED " +
+      "(the signed-in user cannot change their own email here; they use " +
+      "their account screen). Every refusal from EMAIL_TAKEN on, except " +
+      "the SCIM_MANAGED pair, concerns the email only: a rename sent as " +
+      "{ name } alone still succeeds. code NOT_FOUND is an unknown user; " +
+      "code FORBIDDEN a caller without the users.write capability. Email " +
+      "changes are rate-limited per caller: an HTTP 429 arrives as code " +
+      "INTERNAL with status 429 and retryable true, and is never retried " +
+      "automatically, so ask the person to try again later. " +
+      "DirectoryError.reason is the host's specific refusal code, or null " +
+      "when it gave none; branch on it, and show error.message to the person.",
     returnShape: {
       users: "Array<{ id, name, email?, role, is_active }>  // snake_case rows; unwrapped from { data, meta }",
       loading: "boolean",
-      error: "DirectoryError | null  // { code, message, retryable }",
+      error: "DirectoryError | null  // { code, reason, message, retryable }",
       refetch: "() => Promise<void>",
       invite:
-        "({ email, name, group_ids?, send_invitation? }) => Promise<Invite>  // send_invitation: false stores it unsent (status 'not_sent'); rejects with DirectoryError",
+        "({ email, name, group_ids? }) => Promise<Invite>  // rejects with DirectoryError",
       deactivate: "(userId) => Promise<User>  // rejects with DirectoryError",
       reactivate: "(userId) => Promise<User>  // rejects with DirectoryError",
       remove: "(userId) => Promise<void>  // rejects with DirectoryError",
       sendPasswordReset:
         "(userId) => Promise<{ sent, email_masked }>  // rejects with DirectoryError",
+      update:
+        "(userId, { name?, email? }) => Promise<{ id, name, email }>  // at least one key; an email change notifies the user at their previous address; rejects with DirectoryError (reason EMAIL_TAKEN, SERVICE_ACCOUNT_PROTECTED, …; status 429 when rate-limited)",
     },
     requiredContextSlice: ["directory.users"],
     scopes: ["users.read:*"],
@@ -1833,8 +1855,7 @@ const HOOKS = [
   // sc-5097 — pending AppUser invite administration. Returns
   // `{ invites, loading, error, refetch, resend, revoke }`. Reads need
   // `invites.read:*`; resend/revoke need `invites.write:*` plus the
-  // caller's `users.write` SystemAcl capability. sc-9714: `resend` is also
-  // the first send of a `not_sent` invite — there is no separate `send`.
+  // caller's `users.write` SystemAcl capability.
   {
     name: "useInvites",
     signature: "useInvites(query)",
@@ -1844,23 +1865,13 @@ const HOOKS = [
       "directory-client at ctx.directory.invites.{list,resend,revoke}. " +
       "Returns { invites, loading, error, refetch, resend, revoke }. list " +
       "returns the { data, meta } envelope verbatim — the hook unwraps " +
-      "res.data; rows are snake_case (email, status, sent_at, expires_at, …) " +
-      "and status is the server-computed pending/accepted/revoked/expired/" +
-      "not_sent value. not_sent is an invitation created with " +
-      "send_invitation: false that has not been emailed yet: its sent_at is " +
-      "null, it cannot be accepted until it is sent, and its expires_at " +
-      "means nothing yet, so show no expiry for it. resend(inviteId) is the " +
-      "ONE call that sends an invitation — the first send of a not_sent one " +
-      "and a repeat send of a sent one alike: it emails the invitee, stamps " +
-      "sent_at, restarts the 7-day expiry and resolves the row with status " +
-      "'pending'. There is no separate send method; label the button " +
-      "'Send invitation' on a not_sent row and 'Resend' on a pending one. " +
-      "query is { status?, q?, app_user_id?, limit?, offset? } passed " +
+      "res.data; rows are snake_case (email, status, expires_at, …) and " +
+      "status is the server-computed pending/accepted/revoked/expired " +
+      "value. query is { status?, q?, app_user_id?, limit?, offset? } passed " +
       "verbatim; the endpoint defaults to status 'all', so pass " +
-      "{ status: 'pending' } for the usual outstanding-invite list and " +
-      "{ status: 'not_sent' } for the prepared ones; " +
-      "status 'open' is every invite neither accepted nor revoked (pending, " +
-      "not_sent or expired). q is a " +
+      "{ status: 'pending' } for the usual outstanding-invite list; " +
+      "status 'open' is every invite neither accepted nor revoked (pending " +
+      "or expired). q is a " +
       "case-insensitive substring match on the invite's name or email. " +
       "Each row's app_user_id is the id the invitee's user account will " +
       "have once they accept; a USER column may already hold it, and " +
@@ -1877,12 +1888,12 @@ const HOOKS = [
       "refetch on success.",
     returnShape: {
       invites:
-        "Array<{ id, app_user_id, email, name, group_ids, status, sent_at, expires_at, accepted_at, revoked_at, created_at }>  // snake_case rows; status is pending | accepted | revoked | expired | not_sent; unwrapped from { data, meta }",
+        "Array<{ id, app_user_id, email, name, group_ids, status, expires_at, accepted_at, revoked_at, created_at }>  // snake_case rows; unwrapped from { data, meta }",
       loading: "boolean",
       error: "DirectoryError | null  // { code, message, retryable }",
       refetch: "() => Promise<void>",
       resend:
-        "(inviteId) => Promise<Invite>  // sends it (first send of a not_sent invite too); refetches; rejects with DirectoryError",
+        "(inviteId) => Promise<Invite>  // refetches; rejects with DirectoryError",
       revoke:
         "(inviteId) => Promise<void>  // refetches; rejects with DirectoryError",
     },
@@ -3045,7 +3056,7 @@ const WIDGET_CONTEXT_SHAPE = {
       "groups: { list(query?) -> Promise<{ data, meta }>, create(body), remove(id), addMember(groupId, userId), removeMember(groupId, userId), listMine() }, " +
       "invites: { list(), revoke(id), resend(id) }, " +
       "bankid: { status() -> { linked, available }, startLink() -> { order_ref, qr, ... }, collect(orderRef), cancel(orderRef), unlink() } }. " +
-      "users backs useDirectory() + useUsers(); groups backs useGroups(); invites backs useInvites() (list/resend/revoke invites — resend also sends one created with send_invitation: false — gated by users.write:* + the users.write capability); bankid backs useBankIdLink() (REQ-BANKID-AUTH — self-service account linking, JWT-gated, no widget scope). List methods return the { data, meta } envelope verbatim (hooks unwrap res.data); rows/bodies are snake_case. Reads gated by directory.read:users / users.read:* / groups.read:*; mutations by users.write:* / groups.write:* (destructive user removal by users.delete:*).",
+      "users backs useDirectory() + useUsers(); groups backs useGroups(); invites backs useInvites() (list/resend/revoke pending invites, gated by users.write:* + the users.write capability); bankid backs useBankIdLink() (REQ-BANKID-AUTH — self-service account linking, JWT-gated, no widget scope). List methods return the { data, meta } envelope verbatim (hooks unwrap res.data); rows/bodies are snake_case. Reads gated by directory.read:users / users.read:* / groups.read:*; mutations by users.write:* / groups.write:* (destructive user removal by users.delete:*).",
     required: true,
     fields: { users: "object", groups: "object", invites: "object", bankid: "object" },
   },
@@ -5077,7 +5088,14 @@ const CONTRACT = deepFreeze({
   //    `scope: { kind: "granted" }` (the rows the signed-in user reads through
   //    a user or group grant) and the `onAccessGained` / `onAccessLost`
   //    handlers that report rows entering and leaving that set.
-  version: "1.154.0",
+  // 1.155.0: narrowing (sc-10566) — withdraws 1.144.0: `useUsers().invite`
+  //    takes no `send_invitation` and always emails, invite rows carry no
+  //    `sent_at`, and `not_sent` is no longer a status.
+  // 1.156.0: additive (sc-10429) — `useUsers()` gains
+  //    `update(userId, { name?, email? })`, gated on `users.write:*`; the
+  //    linter requires that scope for a `.update(` call beside `useUsers(`.
+  //    `DirectoryError` gains `reason`, the host's specific refusal code.
+  version: "1.156.0",
   sharedTranslationKeys: SHARED_TRANSLATION_KEYS,
   hooks: HOOKS,
   primitives: PRIMITIVES,