Solavel Solavel Docs

Profile and account settings

docs/solavel/settings.md

Who can use this: Any signed-in user URL / Route: /profile and /portal/settings (alias view of the same data) Plan / feature gate: Always on

Purpose

This is where you change your name, email, password, and account details. Two URLs hit the same screens depending on which shell you came from: signed-in users coming from the sidebar reach the page via /portal/settings; older bookmarks pointing at /profile still work.

Step by step

Edit your name and email

  1. Open Profile & Security in the sidebar (/portal/settings, route portal.settings.edit). It is the same page as /profile (route profile.edit).
  2. Update Name or Email. Save (PATCH /profile, route profile.update).
  3. If you changed your email, Solavel sends a confirmation link to the new address. Click it, or open /profile/email/confirm (route profile.email.confirm) — until you confirm, the change does not take effect.

Change your password

  1. From the same profile page, scroll to the Update Password section.
  2. Enter your current password and the new password twice. Save (PUT /profile/password, route profile.password).
  3. You stay signed in on the device you used. Other sessions are not invalidated automatically — sign out everywhere with POST /logout if you want a clean slate.

Update client-level details

If you are the Organization Owner (and therefore the client), the page also shows a Client details section (legal name, contact phone, etc.). Save there with PATCH /profile/client (route profile.client.update). Managers and Members do not see this section.

Delete your account

  1. Scroll to Delete Account.
  2. Enter your password to confirm. Submit (DELETE /profile, route profile.destroy).
  3. Your user is removed and your sessions end. If you are the only owner of a client, deletion is blocked — transfer ownership first, or contact Solavel support.

What is not on this page

  • Two-factor authentication. Solavel does not currently offer 2FA. Tracking it as a future feature.
  • API keys. API keys for the central app are not user-issued; staff create them inside /admin/*. Solabooks has its own per-organization API access page at /finance/settings/api-access.
  • Notification preferences. There is no per-user notification settings page yet. All notifications follow the system defaults.
  • Locale. The central app's locale is fixed to the public site's locale (English) for signed-in users.

Profile data inside Solabooks

Solabooks has its own profile screen for things like preferred currency display and per-organization avatars. Those settings are scoped to the organization, not to your user. Read Logging in and access for how Solabooks receives your identity from the central app.

Permissions / restrictions

  • Sign-in required (auth middleware).
  • Email must be verified before the page is reachable; otherwise you are bounced to /onboarding/verify.
  • The Client details section is gated by the user owning a client record (users.client_id set and the matching users.is_client_owner flag).

Common problems

  • "Password is incorrect." — On the change-password form, the current password field must match what you signed in with, even if you used a "remember me" cookie.
  • The email-change link does not arrive. Check spam, then ask a staff member to re-send via /admin/client-users/{user}/reset-password (resets password, but also re-validates the email). Or wait for the queue to drain and try again.
  • Account deletion is blocked. You are the sole Organization Owner of a client. Use Organizations to add another owner first.
  • Profile changes are not saved. Check that your CSRF token is fresh — sign out and back in if the browser was open for a long time.

Related

Source: docs/solavel/settings.md ← All documentation