Update privacy settings

Outcome

Set archivedContactRetentionDays (30 to 3650) so the scheduled run erases archived contacts that many days after archiving, or null to keep them. Erasure is permanent and keeps only the opt-out (see contacts.erase); at most 25 contacts per workspace are erased per run. Audited.

Before you start

• Verify the intended environment, signed-in credential, authorized organization and the action permission workspace:write.
• Discover and select an authorized canonical Engage workspace. Pass resourceType=workspace and resourceId separately from action input.
• Review the exact effects and obtain approval before CLI --confirm or MCP confirm:true. A local capture does not authorize a live mutation.

Discover the target

topolo whoami --json
topolo actions get app_topolo_engage.privacy.settings.update --json
topolo workspaces list topolo-engage --json

Set ENGAGE_WORKSPACE_ID to the identifier of the selected authorized workspace.

Input contract

Validate, plan and execute

Build payload.json from the current schema and discovered identifiers. The action description above defines its behavior, limits, side effects and declared errors.

: "${ENGAGE_WORKSPACE_ID:?Set ENGAGE_WORKSPACE_ID to your selected workspace identifier}"
topolo actions validate app_topolo_engage.privacy.settings.update --data @payload.json --json
topolo actions plan app_topolo_engage.privacy.settings.update --resource-type workspace --resource-id "$ENGAGE_WORKSPACE_ID" --data @payload.json --confirm --json

Review the plan and approve its exact effects before executing the unchanged request.

: "${ENGAGE_WORKSPACE_ID:?Set ENGAGE_WORKSPACE_ID to your selected workspace identifier}"
topolo actions call app_topolo_engage.privacy.settings.update --resource-type workspace --resource-id "$ENGAGE_WORKSPACE_ID" --data @payload.json --confirm --json

For MCP, use topolo_get_action, topolo_validate_action, topolo_plan_action and topolo_call_action. Pass resource context separately where required; confirm:true is required for mutations.

Captured successful requests and responses

Captured HTTP 200 · archived contact retention > erases only archived contacts past the period in workspaces that set one, and they stay suppressed

Action input

{
  "archivedContactRetentionDays": 90
}

Actual local response

{
  "settings": {
    "archivedContactRetentionDays": 90,
    "updatedBy": "user_1",
    "updatedAt": "2026-10-06T08:30:00.000Z"
  }
}

Source test: archived contact retention > erases only archived contacts past the period in workspaces that set one, and they stay suppressed. Actual route handlers with SQLite repositories; synthetic identity/workspace grants and provider ports.

Captured HTTP 200 · archived contact retention > erases at most one batch per workspace per run

Action input

{
  "archivedContactRetentionDays": 30
}

Actual local response

{
  "settings": {
    "archivedContactRetentionDays": 30,
    "updatedBy": "user_1",
    "updatedAt": "2026-10-06T08:30:00.000Z"
  }
}

Source test: archived contact retention > erases at most one batch per workspace per run. Actual route handlers with SQLite repositories; synthetic identity/workspace grants and provider ports.

Captured HTTP 200 · privacy settings > defaults to keeping archived contacts, updates with audit, and needs write access

Action input

{
  "archivedContactRetentionDays": null
}

Actual local response

{
  "settings": {
    "archivedContactRetentionDays": null,
    "updatedBy": "user_1",
    "updatedAt": "2026-10-06T08:30:00.000Z"
  }
}

Source test: privacy settings > defaults to keeping archived contacts, updates with audit, and needs write access. Actual route handlers with SQLite repositories; synthetic identity/workspace grants and provider ports.

Effects and response meaning

• Set archivedContactRetentionDays (30 to 3650) so the scheduled run erases archived contacts that many days after archiving, or null to keep them. Erasure is permanent and keeps only the opt-out (see contacts.erase); at most 25 contacts per workspace are erased per run. Audited.

Verify the outcome

• Check the response against the declared output schema and the requested operation. For mutations, use the action-specific read described in the action description before any dependent operation.

Recover

For an uncertain result, inspect current retained state with a read action before retrying. Do not replay a mutation unless its contract explicitly guarantees idempotency.

Refused requests

Captured HTTP 403 · privacy settings > defaults to keeping archived contacts, updates with audit, and needs write access

Action input

{
  "archivedContactRetentionDays": 90
}

Actual local response

{
  "error": {
    "code": "permission_denied",
    "message": "The credential lacks workspace:write.",
    "details": {
      "requiredPermission": "workspace:write"
    }
  }
}

Source test: privacy settings > defaults to keeping archived contacts, updates with audit, and needs write access. Actual route handlers with SQLite repositories; synthetic identity/workspace grants and provider ports.

Captured HTTP 422 · privacy settings > defaults to keeping archived contacts, updates with audit, and needs write access

Refused input; do not execute

{
  "archivedContactRetentionDays": 7
}

Actual local response

{
  "error": {
    "code": "invalid_action_input",
    "message": "Input for privacy.settings.update is invalid.",
    "details": [
      {
        "origin": "number",
        "code": "too_small",
        "minimum": 30,
        "inclusive": true,
        "path": [
          "archivedContactRetentionDays"
        ],
        "message": "Too small: expected number to be >=30"
      }
    ]
  }
}

Source test: privacy settings > defaults to keeping archived contacts, updates with audit, and needs write access. Actual route handlers with SQLite repositories; synthetic identity/workspace grants and provider ports.

Error recovery

• HTTP 403 permission_denied: Stop and inspect the current credential and selected resource. It needs workspace:write; do not broaden access or switch organization automatically.
• HTTP 422 invalid_action_input: Correct the request against the current action input schema, then validate it again before planning.

Related actions

• Get privacy settings

Evidence and limits

• /api/privacy/settings

• Actual route handlers with SQLite repositories; synthetic identity/workspace grants and provider ports.

• Widget/bootstrap use actual app handler but mocked worker runtime and app identity.

• No gateway execution, live permissions, external delivery or deployed proof.

These are local route captures with synthetic identity and simulated dependencies. They do not prove live authorization, gateway execution, production state, or external delivery.