Please enable JavaScript to view this site.

Invantive Estate offers a flexibele model to protect the access to data. The security exists of a aggregate of two security mechanisms:

Securing of access to data of projects (project security).

Security of the access to functions like screens and reports (function security).

The aggregate means that:

A user only has access to data in a function if he has access to the data as well as the function.

A user can only change data (change, add or delete) in a function if he has writing rights on the project and also writing rights in the function.

There is no security mechanism to secure access to data which do not belong to projects. The access to the functions decides if someone can see or change the data.

Because of the aggregate, it is possible that a user can change data in one screen, but not in another.

Document security is described in

Project Security

Per project, it can be set if someone can have all data of that particular project:

See

Change

All data of that project means the project itself, and all other data like invoice lines, orders, revenues and project authorizations.

You can maintain the security in several ways:

In the screen Settings you can indicate if everyone can see or change all projects.

In the screen Roles you can indicate if all users with a role can see or change all projects.

In the screen Project Authorizations you can indicate per aggretate of a project and user if someone can see or change the project.

On top of that, you can automatically maintain rights using profile options with the text '-pae-' in the code, so that a controller can get automatically reading and/or editing rights for the project where he is responsible for.

Notice: the user ‘system always has access to all projects.

Function Security

Per function, it can be set or someone:

The screen can open

Data can change in the screen

The function security is set through the screen Role Authorizations.

Notice: the user 'system' always has access to all projects.

Security Documents

The security of the documents is arranged through the combination of project security and function security. There is an additional security mechanism because you can see documents with different types of data like Units, Orders and Revenues in the function Documents

By giving access to the various types of functions for Documents you can determine who is allowed to see which documents. For example, the function 'Access to documents with Project.' yields access to documents with projects if you also have rights for the related project.

For background processes the function 'Access to documents with Background Process.' yields access to the related documents. However, here it is the case that you can always view and edit documents of background processes that you have requested yourself.

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.

  
Disclaimer