Custom modules

What a module is

Opero is made of modules. Some of them are built in and work similarly at every client: contractors, sales invoices, cost invoices, the service catalog, reports. The rest are custom modules, built for the company. They are where the lists live that are named the way they are spoken of in the organization's work: service tickets, leave requests, projects, complaints.

A module is not a screen in itself. It is a drawer in which the objects of a single topic lie. In the menu you usually see not the module, but the individual lists from it, grouped into a folder.

Example. The HR module contains the Employees list and the Leave requests list. In the menu these are two entries; to the system they are one coherent area that can be enabled or disabled as a whole in a given company.

Reasons for limited module visibility

A module is shared separately with each company in the organization. If you work across several companies, after switching the company some areas may disappear or appear. This is not a fault, but a deliberate decision: a trading company does not need a production module.

The second limitation is permissions. Even in a shared module you will see only the lists and records you have a right to.

Consequences for the user

• A new area of work does not require a new program. It arises as a module in the same system, with the same sign-in, the same permissions, and the same search.
• Data from different modules can be linked: a record from one module may point to a record from another, for example a service ticket to a contract.
• If an area is missing or badly divided, that is a matter to report to the instance administrator, not a subject for an IT project.