Data management

Maintaining data consistency is a big challenge for these collaborative and dynamic applications.

While there are no miracle solutions to such challenge, moon ensures consistency by:

considering each individual user, who is at the source of information, as both contributor and beneficiary

promoting collaboration between members of the organization by sharing vital data — in line with internal communication policies — and

keeping a log of changes or journal enabling a precise tracing of the modified pieces of data.

The more moon is used, the more resilient it becomes.

That being said, the following four safeguarding features are in place to maximize your safety.

Look, it's all here

Data consistency

Any piece of information in moon is attached to a unique owner.

The owner (project manager for an order, business developer for a prospect, consultant for a task on a project), is responsible for maintaining the information he/she owns up-to-date.

Data sharing

moon features a journal of changes which allows anyone in the organization to keep track of events in the company (e.g., a new prospect is entered, a deal was recently won, a new employee was hired). Knowing that data will be shared is a strong incentive for quality.

Data traceability

All changes to the status of a record (e.g., the likelihood of a prospect, the end date of a project, the amount charged on an invoice), is recorded in the database.

The full history of changes of a given record, including by whom and when they occurred, can be visualized.

Organize contributors

See what's new in one click

Look back for tracing changes

Data security

Access level to any functionality or piece of information can be configured individually through the set up of groups of users.

One can grant specific rights to create, read, update and delete records. These privileges can be extended even if the user is not the owner or the contributor of the data, but only a simple visitor.

Along with this ownership principle, moon continuously checks the validity of a series of rules (e.g., "If this project is still ongoing, can its end date be in the past?" or "isn't this invoice overdue?" ). When a record does not pass its set of validation rules, a warning is generated and the owner of the record is notified. Each user of moon is presented with its own list of warnings when logging in and the company dashboard presents the list of users with the largest number of warnings.