Well

Reset workspace preference

well_delete_preference

Destructive

Reset one saved workspace preference, so the setting falls back to the workspace default or to none. scope: "member" resets the CALLER's own override; scope: "workspace" resets the workspace value, and the un-namespaced workspace default needs an owner or admin. Only an owner or admin can pass member_id to reset another member's action_trust level.

Known keys: invoice_default_layout, invoice_design, action_trust, preferred_name, form_of_address, mail_sender_choice, timezone, bank_account_offer, invoice_payment_account, payment_link_reconnect_offer, sunday_routines, customer_facts_note_id. For action_trust the namespace is the kind code, and resetting it makes Well ask the person how to treat that kind again, on the next action of the kind. Resetting a level needs no confirmation for action_trust. A reset can lift a member to a workspace default of act_alone, and that is a raise: the server refuses it over MCP, as it refuses any raise to act_alone.

The result includes previous_value: the value the row held before it was removed, or null if there was none.

Input Schema

TableJSON Schema

Name	Required	Description
`key`	Yes	The preference key to reset.
`scope`	Yes	"workspace" resets the shared value; "member" resets the caller's own override.
`member_id`	No	Owner or admin only: the membership_id of the member whose action_trust level to reset. Omit for the caller's own.
`namespace`	No	The subject of the value, e.g. "customer:<id>", or the kind code for action_trust. Omit for none.
`workspace_id`	No	Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which.
`conversation_id`	No	The conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
`idempotency_key`	No	Optional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.
`workspace_scope`	No	Restrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

TableJSON Schema

Name	Required	Description
`key`	No
`error`	No
`scope`	No
`success`	Yes
`namespace`	No
`previous_value`	No
`conversation_id`	No	The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
`newly_connected`	No	Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
`conversation_id_note`	No	Present only when the server opened a fresh lane, stating that no choice recorded earlier was read.
`conversation_id_source`	No	Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.