Organization Settings

Update Task Settings

Set the org's default task visibility and note-taking toggles.

default_visibility is a privilege-sensitive setting: moving it to public exposes every task created afterwards to the whole organisation. Admin-gated, and the handler re-checks the role.

An EMPTY patch is refused (422) rather than no-opped, because an empty body on this route is always a caller bug.

put/org/settings/tasks

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/org/settings/tasks
  • Auth: HTTP bearer

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Request body

default_visibility'public' | 'team' | 'private' nullable

Default visibility for newly created tasks.

notes_anywhere_enabledboolean nullable

When false, hide the global Quick Note shortcut and its command-palette action.

selection_toolbar_enabledboolean nullable

When false, hide the floating 'Add note' bubble on text selection.

mentions_enabledboolean nullable

When false, hide @ autocomplete in note and reply composers.

notify_on_mentionboolean nullable

When false, suppress mention-triggered bell notifications.

parent_completion_mode'manual' | 'auto_complete' | 'require_subtasks_done' nullable

How a parent task completes relative to its subtasks.

Response

Successful Response

dataStudioPayload required

An open envelope for one settings block, document or brand artefact.

OPEN on purpose. These surfaces are configuration and generated content, and both grow: a new toggle on a settings block or a new field on a generated document must reach a caller on the day it ships, not on the day somebody remembers to widen a mirror. A closed response model here would silently DROP the new key, which reads to the caller as "the product does not have that setting".

The request side is the opposite and is mirrored exactly - see the module docstring for why the asymmetry is deliberate.

Changes

No recorded changes to this operation across all 2 revisions of this API.