First steps in Opero
Co zrobić w pierwszym dniu pracy z systemem: od zaproszenia i logowania, przez sprawdzenie profilu i firmy, po odnalezienie przypisanych zadań i pierwszego rekordu.
Invitation and sign-in
You start with an invitation that arrives at your company e-mail address. The invitation leads to setting up access, and from then on that address is the user's identity in the system.
The account is personal. It is not a departmental or shared access. Every action you take is signed with your first and last name: the team is meant to know who entered what.
Five minutes to start
Before you begin working, go through a short list. It saves a lot of confusion in the first week.
- Complete your profile. Your first and last name are visible next to the records and tasks you enter. Check your e-mail address too, because notifications go there.
- Set the language. It changes the interface labels; it does not change data entered by the team.
- Check which company you are in. If the organization runs several companies, this is the most important habit to start with.
- Look at your tasks. This is usually the first thing you open every day.
- Browse the menu without clicking anything hastily. It is worth seeing first what is where.
Look around before you start entering data. The first impulse is usually "I'll create a record and see what happens." It is better to first look at a few existing records in the area you are to work in. You will see how the team describes data and avoid entering something in a different style from the rest.
Sources of tasks and notifications
Work reaches the user from two sources.
| Source | What it means |
|---|---|
| Tasks | a matter directed to the user by a person or a process |
| Notifications | something happened that you should know about |
A task requires action and waits until you complete it. A notification usually only informs. This difference matters: the task list is work to be done, and notifications are information.
The first record
When it comes to entering something of your own, remember three things.
- Fill in the descriptive fields sensibly. A record's name is not the place for a shorthand that only you understand. Six months from now someone will be searching for it.
- Check the company before saving, if you work across several.
- Do not be afraid to save. A record can be completed later, and the system records the change history, so nothing is lost for good.
Example. Instead of naming a record "New 2", name it the way you would in a conversation with a colleague: "Service contract Kowalski, March". This is one of those things that cost five seconds and save the team hours of searching.
Practices not recommended at the start
- Do not create "trial" records in production. They stay in the lists and someone later counts them in reports. If you want to practice, ask the administrator to point out a place.
- Do not work under someone else's account, even when someone suggests "because it's faster".
- Do not correct other people's records without agreement, until you know how the team works.
No access to an area
This is the most common question in the first week, and it is usually not a fault. The reason is often the access scope for a given role, a different company, or an area not enabled in the company. Ask the administrator, stating specifically what you are looking for and why.
Related
Account and profile describes the account settings. Getting oriented in the system describes the screen layout and navigation. My tasks describes the list of matters awaiting the user. Creating and editing a record describes entering data. Roles and permissions describe the access scope.
Scope and layout of the documentation
Spis sekcji dokumentacji z zakresem każdej z nich, punkt wyjścia w zależności od rodzaju zadania, znaczenie powtarzających się elementów oraz to, czego te strony nie opisują.
Getting oriented in the system
Z czego składa się ekran Opero, czym różni się lista od formularza rekordu, jak działa nawigacja i wyszukiwanie oraz gdzie szukać rzeczy, których nie ma w menu.