M/Workbench is the cockpit of the Series M/, the control center for the creation and maintenance of all resources. It controls the entire document process from document creation to the output processes of output management. Therefore M/Workbench, which is technically implemented as an Eclipse plug-in, also has a strongly organizational side. It helps the administrator to overview and control even extensive and branched projects of customer communication. With M/Workbench you can efficiently and effortlessly convert the requirements of a modern CCM into resources. These ensure that document processes run smoothly and, as far as possible, automatically.
M/Workbench guides the administrator through the entire document creation, processing and output process in a uniform graphical development environment.
The supervisors in particular benefit from the declarative approach in the new operating concept: activate and configure functions simply and intuitively (graphically) instead of implementing them with complex scripting. This simplifies operation and saves time. In addition, the standardized solutions are easy to understand and can be easily communicated to colleagues.
The strong organizational side of M/Workbench also helps the administrator to overview and master even extensive and branched applications or "projects" in customer communication.
The "M/USER" perspective within M/Workbench is used to manage the user profiles and access rights for the affiliated company or companies. The data areas
can be used to define and control the profiles and authorizations in the company down to the lowest level.
An even higher level of detail in work control can be achieved through the metadata that is linked to resources at the project level. They determine, for example, which canned text is available to which user in which business transaction, or whether he or she is allowed to insert additional text at all.
Since the resources of all company documents are created with M/Workbench, the responsible department is often dependent on the technical and content cooperation from other departments. Such subtasks can be integrated into the creation process via role profiles, e.g. via technical authors with different competencies and authorizations.
When Series M/ is operated by a service provider on behalf of different customers with different layouts and text applications or for operation in the cloud, multi-client capability is essential. Depending on the organizational requirements, different operating modes can be used:
If several clients are operated in a common instance, it is necessary to manage client-specific templates and resources separately in the project structure.