Profile — where your account lives

Profile is your personal corner of the tracker: name, email, avatar, password, API token, and how the interface looks. Nothing team-related lives here — invites, roles, and shared stats belong to the Team screen, not this one. This page is only about you.

The screen has four tabs: Account, Security, API, and Interface. Here's what each does and how not to break anything.

One thing on this page actually matters — the API token. Everything else you can change a hundred times and change back. The token: copy it and save it, kitten. Seriously.

The "Account" tab

Core account data and contacts. Everything saves with the single Save button at the bottom of the tab.

The "Account" tab: name, email, language, avatar, and contacts — all saved with one button.

Fields:

Name — required. Can't be blank: the save won't go through and the field is flagged.
Email — checked for uniqueness (no two accounts share a mailbox). Note: changing your email reloads the session — after saving you'll be re-logged-in under the new address. That's normal, don't panic.
Language — the account language. Always shown.
Timezone — only works if the install has the site.utz flag on. If it's off (as on most installs), the field may not render or may do nothing — that's not a bug, the server simply ignores timezone on such an install.
Skin / theme — available if the install ships skins. The primary theme switch lives on the Interface tab anyway — use that one.
Avatar — upload a file and the server crops it for you. To remove it, tick remove avatar. Because of the file upload, this tab saves as a multipart form (you don't need to think about it — just know why saving with a picture is a touch heavier).
Contacts — Telegram, WhatsApp, and other contact meta fields. Fill them as-is; these are your contacts visible to your team.

Edit your account and contacts — step by step:

Open the "Account" tab.
Change what you need — name, email, language, contacts.
To change the avatar, click the upload field and pick a file; to remove the old one, tick remove avatar.
Click "Save".
Wait for the green success toast. If you changed the email, you'll be re-logged-in — expected.

Saving always overwrites language and theme, even if you didn't touch them — the form sends them every time. This doesn't affect you (it re-sends the current value); just don't be surprised that "I never changed the language, yet it saved."

The "Security" tab

Password change only. Two fields: Password and Confirm.

The password is applied only when both fields match. If they differ, the field turns red, the message "Passwords do not match" appears, and the save button is disabled. Nothing is submitted until they match.

Password change: applied only when both fields match.

Change your password — step by step:

Open the "Security" tab.
Enter the new password in Password.
Repeat it in "Confirm" — character for character.
Make sure there's no red highlight and the save button is active.
Click "Save".

Yes, we make you type the password twice. No, it's not because we don't trust your fingers. Well… maybe a little.

The "API" tab

Your API token for accessing the tracker programmatically. Shown read-only in the format {user_id}-{api} (e.g. 1-d6a88a67…). Next to it, a Copy button.

The token isn't hidden behind asterisks or masked — same behaviour as classic.

The second button is Regenerate. It issues a new token and instantly destroys the old one.

The API tab: a read-only token in id-key format (shown as an example value), with Copy and Regenerate buttons.

Copy the token:

Open the "API" tab.
Click "Copy" next to the token field.
The token goes to your clipboard and a confirmation toast appears. Paste it where you need it.

Regenerate the API token — step by step:

Open the "API" tab.
Click "Regenerate".
Confirm in the dialog: "Generate a new API token? The old token will immediately stop working everywhere it is used."
You get a new token. The interface picks it up in memory right away and keeps working.
Immediately update the token in every script, integration, and postback that uses the old value.

Regenerating breaks the old token instantly and everywhere. The moment you confirm, the old value is dead. The interface itself survives this fine (it swaps the token in memory on the fly), but any external script on the old token gets a 401 on its very next request. Don't press this button "just to look." If you pressed it, go update the token in every integration.

This is the one thing on the whole page you must write down somewhere. A name you can retype, a theme you can re-toggle — but a fresh token won't be shown this conveniently in the clear anywhere else. Copy it and save it, kitten. Write it down.

The "Interface" tab

Settings for how Lighter looks and behaves for you personally. They all save automatically — there's no separate button.

Theme, language, and sidebar save themselves. At the bottom: the exit to classic.

Settings:

Theme — system / light / dark. Switches live, you see the result instantly.
UI language — the language of the SPA itself. Changes on the fly; every string redraws.
Default sidebar — collapsed or expanded on your next visit.
Classic interface — the switch that takes you into the real AlterCPA Lite interface — the one with the correct, native words: поток → путь → сайт (flow → path → site).

Switch theme, language, or sidebar — step by step:

Open the "Interface" tab.
Pick a theme, UI language, or sidebar state.
The change applies at once and saves itself.
Settings survive a reload — nothing to press on purpose.

Changing several settings in a row? Don't worry — they accumulate and save as a batch, so nothing is lost. (Earlier, two changes within half a second dropped the first — fixed now.) One caveat: don't hard-reload the page in the first half-second after your last change — that's the one moment the last change might not make it to the server.

Leave for the classic interface — step by step:

Open the "Interface" tab.
Click the "Classic interface" switch.
Confirm the switch.
You're taken into the real AlterCPA Lite interface. To get the familiar labels back, use the "Inclusive design" button in the classic menu (bottom of the sidebar) or the block on the classic profile page.

This isn't "a step back to something hard" — it's graduation. The classic AlterCPA Lite interface is the real, correct one, and the words there are the native ones: what's labelled campaign here is a поток / flow there; the flow here is a путь / path; the landing here is a сайт / site. Once you're comfortable in Lighter, you've earned the real words. Lighter did its job.

The Classic interface button is basically the off-switch for Inclusive Design. Grown into the real words? Flip it — we're glad. When you want the familiar labels back, a quiet little greyed-out button with an accessibility glyph is waiting at the bottom of the classic menu. One click and you're back with the cats.