Update organization-user settings
Update the authenticated user’s per-organization settings.
Merge semantics:
- The payload is merged per key (dot-flattened): only the paths present in the request change; everything else is untouched. Send only what changed.
- Array lists replace wholesale — e.g.
embeddedTablesis one opaque value. Always read-modify-write the full list; sending a partial list deletes the missing entries. - Values equal to the server-side default are elided from storage (and come back via the defaults merge on read — semantically identical).
Keys are whitelisted server-side (OrganizationUserSettingsRequest).
Unknown keys are silently dropped — the request still returns 200, so
verify persistence via the response body, which is the full merged settings
object (same shape as GET).
Plain JSON — this endpoint is not JSON:API.
Autorisierungen
The access token received from the authorization server in the OAuth 2.0 flow.
Header
Bearer Token
Abfrageparameter
Organization ID
Body
Per-user-per-organization settings blob, read and written as plain JSON via
GET|PUT /api/settings/organization-user (not JSON:API). Reads return stored
overrides deep-merged over server-side defaults; writes merge per dot-flattened
key, except array lists, which replace wholesale. Keys are whitelisted
server-side — unknown keys are silently dropped. Only the table/view-related
keys are documented here; the full whitelist (notification preferences, legacy
per-area filter state, calendar settings, …) lives in
app/Http/Requests/Settings/OrganizationUserSettingsRequest and
app/Enums/Settings/OrganizationUserSettingsType. See the "Table State
Persistence" guide for the full contract.
UUID of the active view for the bookings area
UUID of the active view for the orders area
UUID of the active view for the customers area
UUID of the active view for the resources area
UUID of the active view for the invoices area
UUID of the active view for the calendar area
UUID of the active view for the plan-subscriptions area
UUID of the active view for the booking-passes area
Per-user column layout for embedded (area-less) tables. A list keyed by
a free-form id string — not a map, because the settings merge
dot-flattens objects and would corrupt ids/keys containing dots or slashes.
Replaced wholesale on every write: always read-modify-write the full list.
Antwort
OK — the full merged settings object after the update
Per-user-per-organization settings blob, read and written as plain JSON via
GET|PUT /api/settings/organization-user (not JSON:API). Reads return stored
overrides deep-merged over server-side defaults; writes merge per dot-flattened
key, except array lists, which replace wholesale. Keys are whitelisted
server-side — unknown keys are silently dropped. Only the table/view-related
keys are documented here; the full whitelist (notification preferences, legacy
per-area filter state, calendar settings, …) lives in
app/Http/Requests/Settings/OrganizationUserSettingsRequest and
app/Enums/Settings/OrganizationUserSettingsType. See the "Table State
Persistence" guide for the full contract.
UUID of the active view for the bookings area
UUID of the active view for the orders area
UUID of the active view for the customers area
UUID of the active view for the resources area
UUID of the active view for the invoices area
UUID of the active view for the calendar area
UUID of the active view for the plan-subscriptions area
UUID of the active view for the booking-passes area
Per-user column layout for embedded (area-less) tables. A list keyed by
a free-form id string — not a map, because the settings merge
dot-flattens objects and would corrupt ids/keys containing dots or slashes.
Replaced wholesale on every write: always read-modify-write the full list.