Roles & Architecture
Overview of Maecos’ SaaS architecture and permissions-based access model, enabling organizations to define their own roles and manage secure access.
Tenant architecture
Maecos is delivered as a multi-tenant SaaS platform.
Each customer operates in an isolated environment with a dedicated URL: https://[tenant].maecos.com
Data isolation: All customer data is fully separated at the tenant level.
Login configuration: Each tenant can choose between Maecos-managed accounts or Single Sign-On (SSO).
Branding options: Tenants can apply custom login communication and a branded image on the login screen.
This model ensures security, scalability, and flexibility for global deployments.
Permissions-based access
Instead of fixed roles, Maecos uses a fine-grained permissions framework. Organizations are free to define their own roles by combining permissions that control access to features and data.
Example permissions
Actions
Can create actions
Can view all public actions
Can view own actions
Can view assigned actions
Documents
Can view DMS
Can create DMS documents
Can manage DMS
Issues
Can view all issues
Can view team issues
Can assign issues to workstations
A full overview of available permissions is provided in the Permissions Reference.
Typical role groups
While every organization can define its own roles, the following groups are common in practice:
Operators → Create and complete issues, follow checklists, access documents and training.
Team Leaders → Oversee team issues, approve documents, follow up on actions and training needs.
L&D / HR Administrators → Configure skills, manage qualifications, and monitor learning progress.
IT Administrators → Manage integrations, user provisioning, and SSO setup.
Partners / Implementers → Support rollout, configuration, and continuous improvement programs.
These examples provide a starting point for role design, while giving organizations the freedom to align access control with their own governance models.
Architecture in context
Maecos is cloud-native, modular, and designed for seamless integration into manufacturing IT/OT landscapes. Details on technical integrations, API access, and security standards are available in the Technology & Integrations section.
Last updated