Join the LadVen OS testing programRequest a demo
Skip to main content

Profile and personal settings

The profile controls how you appear to the team and how the portal behaves for you: name, contacts, language, timezone, password, avatar, notifications, app background, and the separate password for Disk WebDAV access.

Keep the profile current. Wrong language, timezone, contact data, or notifications quickly becomes missed deadlines, wrong assignments, and unclear communication.

Where to work

Where to work — conceptual guidance, not UI evidence

Open Profile (/profile) from the user menu or side navigation. Available blocks can depend on portal settings, browser capabilities, and access rights.

Main blocks:

  • personal data, position, phone, birth date, and avatar;
  • interface language and timezone;
  • account password;
  • WebDAV app password for Disk;
  • desktop and mobile app background;
  • notification channels and Do Not Disturb;
  • notification domains: Tasks, CRM, Chats, Mail, and Documents.

First login

First login — conceptual guidance, not UI evidence

After the first login, check the profile before active work:

  1. Make sure your name is clear to colleagues.
  2. Fill in work position and phone if the company uses them.
  3. Choose a personal interface language or keep the portal language.
  4. Check the timezone.
  5. Change the temporary password if an administrator gave you one.
  6. Review notifications for tasks, CRM, and documents.

If the profile opens with another person's data, do not edit it manually. End the session and contact an administrator.

Regular Profile Review

Regular Profile Review — conceptual guidance, not UI evidence

Review the profile beyond the first login. Repeat the check when a person changes department, role, country, device, browser, or work schedule:

  • name, position, and contact data are clear to the team;
  • language and timezone match the current work setup;
  • notifications stay enabled for processes where you own the result;
  • WebDAV password is regenerated if a device or access may have been exposed;
  • avatar and background do not reveal documents, clients, QR codes, addresses, or personal data.

If a setting affects deadlines, acceptance, clients, or security, verify it immediately after the change, not at the end of the day.

Personal data and avatar

Personal data and avatar — conceptual guidance, not UI evidence

Name, position, phone, and avatar help colleagues understand who owns work. Profile handles personal data; department, role, admin rights, and workspace access are normally managed by an administrator in Employees, Departments, Workgroups, and access policies.

You can add a birth date in the profile. Based on it, a celebratory badge appears next to your avatar in the employee directory on the day of your birthday — without the year and only on that day. This is personal data: enter the date only if you're comfortable with colleagues seeing the badge. Whether birthday badges show in the directory is something each employee turns on or off for themselves — it's a personal viewing setting, not a company-wide policy. If the date is entered incorrectly, the portal will flag it with a clear message.

Use a neutral avatar without documents, passes, QR codes, phone numbers, private addresses, or client materials.

Interface language

Interface language — conceptual guidance, not UI evidence

The profile language controls the portal interface for a specific user. If the portal option is selected, the user inherits the company's shared language. If a personal language is selected, the portal shows the interface in it when that locale is available.

Use a personal language when an employee works in a language different from the company's main language. After changing the language, reload the page and check that menus, tasks, CRM, and notifications appear as expected.

If part of the interface stays in another language, record the route and screen. Such an issue must be fixed in the product, not worked around in documentation or screenshots.

Timezone

Timezone — conceptual guidance, not UI evidence

The timezone affects task deadlines, the calendar, reminders, event history, SLA, and message times. Check it right after the first login, especially if the team works across different countries.

If task deadlines look shifted, first check the timezone in the profile, then the calendar and browser settings. Do not change task deadlines just to compensate for a wrong timezone.

Account password

Account password — conceptual guidance, not UI evidence

Change the password only through the profile and never send it through files, chats, or tasks. If the portal requires the current password, enter it first and then the new one. If access must be given to another employee, create or restore that account through user administration.

Security and 2FA

Security and 2FA — conceptual guidance, not UI evidence

The profile includes a multi-factor security block: activation requires the current password, a TOTP authenticator, and saved recovery codes. Trusted devices, disabling, and reset are covered in the 2FA guide. Never show a QR code or recovery codes in screenshots.

WebDAV password

WebDAV password — conceptual guidance, not UI evidence

Disk WebDAV uses a separate app password. Your main account password does not work for WebDAV. The app password is shown only when issued or regenerated, so store it in a password manager immediately.

Use WebDAV when a Disk space must be mounted as a network drive in Finder, Windows Explorer, or a file client. Before connecting, verify that it is the correct Disk space and that you understand its access limits. If the password may be exposed, regenerate it. Do not publish screenshots with WebDAV login, email, or generated password visible.

Notifications

Notifications — conceptual guidance, not UI evidence

In the profile you can configure toast notifications, browser push, sound, tab counter, Do Not Disturb, and important notifications during Do Not Disturb.

The Email switch appears only when the system email profile is configured and enabled and the mail transport is available. If the channel is unavailable, the profile shows the reason and keeps the switch disabled; this is not a failure to save your personal settings.

Notification domains include:

  • Tasks - assignments, comments, reactions, checklists, and task changes.
  • CRM - assignments, client messages, mentions, comments, stages, and fields.
  • Chats - messages, mentions, incoming and missed calls.
  • Mail - new messages.
  • Documents - updates, signatures, inbound exchange, and signing states.

Do not turn everything off without a reason. Critical task, client, and document events should stay visible.

Browser push permission

Browser push permission — conceptual guidance, not UI evidence

Push depends on two levels: the profile setting and the browser permission. If the browser blocks push, the profile cannot deliver it.

If push does not work, follow this order:

  1. Check the permission status in the profile.
  2. Allow notifications for the work domain in the browser.
  3. Enable push and the needed domains in the profile.
  4. Check Do Not Disturb.
  5. Reload the page and verify delivery with a safe test event.

App background

App background — conceptual guidance, not UI evidence

The app background is a personal visual setting. You can use separate desktop and mobile images. Choose calm images that do not make tasks, CRM, documents, or messages harder to read.

Do not upload backgrounds with private data, client documents, chat screenshots, technical addresses, QR codes, or internal diagrams.

Surface effects

Surface effects — conceptual guidance, not UI evidence

The profile can set surface effects for the current browser: Auto follows system or device preferences, Glass keeps transparency and blur enabled, and Solid/Performance disables them. Auto may switch to a simplified look when the device or system requires it. This changes appearance only, not task, CRM, or document data; choose Solid/Performance if the interface feels slow.

Troubleshooting

Troubleshooting — conceptual guidance, not UI evidence

ProblemCheck
UI is in the wrong languageProfile language, portal language, page reload, localization for the screen.
Deadlines look shiftedProfile timezone, calendar, browser or device timezone.
Push does not arriveBrowser permission, push setting, notification domain, Do Not Disturb.
Password change failsCurrent password, new password rules, account status.
WebDAV does not connectApp password, correct login, access to the Disk space, regenerated password.
Background hurts readabilityDisable it or upload a calmer image for desktop/mobile.

Screenshot safety

Screenshot safety — conceptual guidance, not UI evidence

Use only a demo account for profile documentation: neutral name, position, avatar, training email and phone, masked passwords, safe WebDAV state without a visible generated password, neutral background, localized UI, and notifications without real clients, documents, emails, or people.

Do not publish screenshots with real email, phone, login, WebDAV password, private links, real files, technical wording, or mixed languages.

Good practices

Good practices — conceptual guidance, not UI evidence

  • Check language and timezone after first login.
  • Keep name, position, and contacts clear.
  • Keep deadline- and client-related notifications enabled.
  • Recheck browser push permission after changing device.
  • Regenerate the WebDAV password if there is any doubt.
  • Reload the page after important settings changes.

Related scenarios — conceptual guidance, not UI evidence