Skip to content
JiraVision

Account & workspace setup

Profile, password, sessions, preferences and the settings audit feed.

Account & workspace setup

/dashboard/settings is the personal control centre. It is organised into cards, each backed by a real read/write endpoint.

Profile and account

  • Profile: name, role, timezone and bio. Saves through PATCH /api/user/profile.
  • Avatar: upload with POST /api/user/avatar/upload, remove with POST /api/user/avatar/remove.
  • Account: shows the email the session belongs to. Changing it requires a password confirmation.

Password and sessions

  • Security · password posts to /api/auth/forgot-password, which issues a reset token and emails the link. The link lands on /reset-password and posts to /api/auth/reset-password.
  • Sessions shows the session mechanics: a 24-hour idle timeout, a 30-day absolute limit, and the one cookie involved. Ending it calls POST /api/auth/logout, which revokes the auth_sessions row.

Preferences and defaults

  • Preferences: theme, density and language. Persisted per user through /api/settings/<key>.
  • Task defaults: the status, priority and story points pre-filled on the create-task form.
  • Notifications: which event types reach your bell. Workspace-wide notification switches live in /dashboard/team/settings instead.

Data and safety

  • Data export downloads your own records. Bulk dataset export is documented in the data export doc.
  • Settings audit feed lists every settings write with the actor and timestamp — the same pattern the team role audit log uses.
  • Danger zone: requesting account deletion checks that you have no open assigned tasks, records a deletionRequestedAt flag and a system notification for manual review. You can cancel the request before review.

Workspace-wide settings

Team name, workspace notification switches and role governance live in /dashboard/team/settings and are restricted to admin and super-admin roles.