Skip to main content

User settings

User Settings control your own account experience. They do not change organisation-wide policy, server configuration, or another member's access.

Open User Settings from the account menu to manage profile details, appearance, chat defaults, active sessions, access tokens, ticket preferences, and personal Agent availability.

Profile​

Your profile is the identity other members see across chat, tickets, docs, reviews, and organisation membership lists.

You can manage:

  • First name and last name.
  • Active-organisation title.
  • Profile image.
  • Generated avatar style and seed.

Admins can manage member profile fields from Organisation Settings. When an admin locks first name, last name, or title, the affected member sees the field as managed and cannot edit it unless they also have organisation admin permission.

info

Profile image uploads are stored as file attachments. They follow the same upload storage, size, and access rules described in Uploads and media.

Appearance​

Appearance settings are saved to your account and used when you sign in from another device.

The Theme section controls:

  • Color mode: system, light, or dark.
  • Theme preset: the color palette used by the app.

The Layout section controls whether the sidebar starts expanded on desktop.

The browser may use local storage as a first-load fallback while your saved account settings are loading. After sign-in, the server-side user setting is the source of truth.

Chat​

Chat settings control your own AI chat defaults without changing anyone else's workspace.

Default Chat Assistant chooses the chat assistant selected when you open Chat. Server, organisation, and project admins can make additional Chat Assistants available.

Agents​

The Agents tab controls personal Agent availability where the server, organisation, and current project allow it.

You can:

  • Disable an Agent for yourself.
  • Re-enable an Agent only when no higher level has disabled it.
  • Tune supported personal schedules such as interval-based operating pulses.

If a row is disabled by a higher level, the reason names whether server, organisation, or project settings must change.

See Agent configuration for the full inheritance model and built-in Agent catalog.

Tickets​

Ticket settings control your personal ticket defaults.

Auto assign AI-created tickets to me assigns tickets created by AI actions to your user account by default.

Sessions​

The Sessions tab lists your active TOW browser sessions. Each row shows basic session metadata including creation time, last seen time, expiration time, authentication method, active organisation, browser user agent summary, and last IP address.

You can log out another session or log out all other sessions. Logging out a remote OIDC-backed session invalidates the TOW session only. Signing out from the current browser still uses the configured OIDC provider logout flow when provider logout is enabled.

Access tokens and MCP​

The Sessions tab also manages personal access tokens. A token is bound to one organisation and can authenticate API clients, including chat apps that connect to TOW through MCP.

TOW shows a new token secret once. Copy it before selecting Done; an existing secret cannot be revealed again. Each saved row shows its identifying prefix and suffix, expiry, last use, IP address, organisation, and client. Revoke a token immediately if its client is lost or no longer trusted.

warning

Personal access tokens carry all of the user's privileges through the full REST API, including server-admin authority when applicable. The selected organisation becomes active, but the token is not restricted to the MCP tools shown by a chat app. Use a dedicated, expiring token for each integration and store it as a secret.

The MCP setup panel provides the public /api/mcp endpoint and a generic remote HTTP configuration. This release supports clients that can send the PAT in a custom Authorization: Bearer … header. OAuth and hosted clients that cannot set custom headers are deferred.

See Connect a chat app with MCP for the complete setup, security, approval, and troubleshooting flow.

When settings do not change immediately​

Most user settings apply as soon as they are saved. If a page was already open, refresh the page when you do not see the change.

If a profile field is disabled, check whether an organisation admin has locked it.

If an AI action is disabled, open Agents and check the effective reason. User settings cannot override a server, organisation, or project disable.