User account and profile

Zawartość profilu użytkownika, znaczenie danych kontaktowych dla zespołu, ustawienie języka pracy oraz czynności przed urlopem i przy zmianie stanowiska.

The scope of profile data

A profile looks like a private matter, but in practice it is an element of teamwork. From it the system takes the data others see: at an assigned task, at a comment, at a record you created.

Three things in the profile affect others more than it seems.

First and last name. They appear everywhere the author is shown. An abbreviation or a nickname makes work harder for people looking for whom to talk to about a matter.
E-mail address. Notifications from the system go to it. An outdated address means you stop getting information about tasks.
Phone. It is sometimes the only way to reach you in an urgent matter.

The working language

In the profile you set the language you work in. The change concerns the interface: the names of buttons, the menu, the system's messages.

It does not change the data entered by the team. A record described in Polish stays in Polish regardless of the language you set, unless someone has prepared a translation for it. This distinction is worth knowing, because it is sometimes a source of misunderstandings in international teams.

Account security

An account in Opero gives access to the company's data, so treat it like access to company mail.

Do not share the account. Working under someone else's account means the records' history attributes changes to the wrong person, and that spoils work for everyone.
Enable extra sign-in confirmation, if the organization uses it. It is a few seconds at sign-in and a real difference in an attempt to take over the account.
Report a suspicious sign-in to the administrator, instead of waiting for it to "sort itself out".

An account is not a shared mailbox. An account created "for the department" is the wrong solution: the system stops showing who actually made a change, and at the first dispute about data there is no way to reconstruct it.

A user's absence

Leave or a longer absence require one action: assigned tasks do not disappear. They wait until you return, or they block a matter for someone else.

Before a longer absence, review your tasks and arrange with your manager who will take them over. Reassigning a task is an ordinary operation, but someone has to know about it in advance.

Example. A leave request awaits approval from a person who is themselves on leave. The matter stands until their return, because no one else has this task on their list. That is why a substitution is arranged before the trip.

A change of position or departure

When you change your scope of duties, permissions do not change automatically. Ask the administrator to adjust the access: it is usually a matter of adding one area and removing another.

On leaving the company, the account is deactivated, but the entries and history remain in the system. This is normal and needed: documents must stay complete and the history consistent.

Roles and permissions describe the access scope granted by the administrator. My tasks describe the list of matters awaiting the user. Notifications describe messages sent to the address from the profile. Change history describes the record of authorship of changes.