A person is a master data record in which persons are specified in MYDAS. Generally a person does not necessarily have to be a user. MYDAS is used by many clients as a CRM system in which all business contacts are recorded. This explains the separation of user and person.

A person can also have several users. If, for example, a user is a normal operator and at the same time takes over administrator functions, it is recommended for compliance reasons to separate these user functions from another. In this case, the person gets an account for his role as a user and an account for the role as administrator.

The user is the access to the system. Ultimately, all access conditions to MYOC are regulated in the user master data. The most important ones are:

1. User name
2. User password
3. User function

But also other access conditions like the password regulations:

can be individually regulated in the user master data. In general, however, this data is controlled centrally and preassigned in the fields.

The profile bundles the individual rights into a package. This simplifies the administration of rights. A user has a set of profiles that control the scope of his or her rights in the system. Profiles are always managed centrally.

Via function the access rights to certain modules are controlled. For example, an ADMIN user has no restrictions on modules, but an agency user only has access to the modules he needs for his activities.

The individual right is the smallest unit in this system. A right controls what the user can do down to field level, for example, INSERT, UPDATE, DELETE.

It is not possible for a user to be assigned individual rights. Rights are always linked to profiles. Rights are defined by Cataneo and cannot be changed by the customer.

Usually, rights are assigned to the profiles of Cataneo.