The M42 Professional Service Management platform allows organizations to digitalize and automate IT and enterprise services, utilizing a flexible data model and configurable workflows. The tool can be seamlessly incorporated into different domains and adapt to evolving needs. Organizations can create customizable data models tailored to their specific requirements, including things like modern service management, which ensures system maintenance, cost reduction, and robust data security. With an open API, the M42 Professional Service Management platform can be connected to any system or application to automate more processes end-to-end.

M42 Professional Service Management Platform Structure

The M42 Professional Service Management platform tool consists of the following three elements:

• Templates
• Folders
• Users and their permissions

Templates form the basis for information management in the system and are the highest-level units of the data model. Templates are freely modifiable entities that define the structure and the information content of data cards. Data cards are instances of the actual data that is stored in the system. 

All information in the M42 Professional Service Management platform is stored as data cards within folders. The application uses a hierarchical folder structure. You can modify the folder structure freely. That is, you can create, modify, and delete folders to meet your organization's needs.

Users’ permissions are assigned according to their roles. Each user belongs to at least one role. The user’s permissions to access information are determined by these roles.

Permissions are divided into administrator, module, template, attribute, and folder permissions.

• Module permissions determine the modules that the user can access. When logging in, the user needs a free license for each of these modules. Administrator permissions grant the user the rights necessary to perform administrative operations.
• Template permissions control the user’s access to data cards. That is, the user can see the data cards created from templates to which the user has access.
• Attribute permissions control what the user can see on a data card. That is, you can give the user access to only some fields of the data card, allowing them to see only the permitted attributes.
• Folder permissions control which sections of the folder structure the user can access. The folder permissions overlap partly with the template permissions. If the user does not have permission to a folder, they cannot see it at all, nor can they see the data cards in the folder. However, the user can have permission to access the templates for the data cards. If the user has permission to a folder, they can see data cards created from templates they can access.