Settings
Settings provides a place to manage platform settings. Consider the effect on business work before making a configuration decision.
Which setting needs attention?

User and tenant administration, configuration control and operational records for the platform.
Book a demoPlatform administrators and business system owners.
Settings provides a place to manage platform settings. Consider the effect on business work before making a configuration decision.
Which setting needs attention?
Tenant Settings helps administrators organise tenant-level settings. Review tenant decisions alongside the organisation’s deployment arrangements.
Which settings belong at the tenant level?
Users provides a place to administer platform users. Consider each user in the context of their business responsibilities.
Which user arrangement needs updating?
Config Control helps teams organise control of configuration work. Discuss the intended change with the people responsible for the platform.
What configuration decision are we making?
Org Chart provides a place to describe organisational structure. Use the structure as a reference when discussing responsibilities.
How is this team positioned in the organisation?
Notifications helps teams organise platform notifications. Consider who needs the information in the context of the work.
Which notification needs attention?
Audit Log provides a place to review logged platform activity. Use recorded activity as an operational reference when discussing the platform.
What recorded activity should we examine?
Integration Notes provides a place to keep notes about integration arrangements. Document the business context of an integration without assuming a particular connected product.
What should colleagues know about this integration?
| Module | Typical business question |
|---|---|
| Settings | Which setting needs attention? |
| Tenant Settings | Which settings belong at the tenant level? |
| Users | Which user arrangement needs updating? |
| Config Control | What configuration decision are we making? |
| Org Chart | How is this team positioned in the organisation? |
| Notifications | Which notification needs attention? |
| Audit Log | What recorded activity should we examine? |
| Integration Notes | What should colleagues know about this integration? |
Consider Admin alongside the families that share its business work. Select the modules required, then discuss the workflow and integration arrangements between teams.
Every module is AI-ready and works without AI or with AI. Your organisation decides whether to use AI; it is not a prerequisite.
Deploy MetisOne on-premises or in your organisation’s own private cloud.
MetisOne works standalone for corporate workflow setup and integrations, without ARX or AERIX. It can also connect to ARX and AERIX for private and hybrid AI.
User and tenant administration, configuration control and operational records for the platform.
Platform administrators and business system owners. This family includes Settings, Tenant Settings, Users, Config Control, Org Chart, Notifications, Audit Log, Integration Notes.
Yes. Every Admin module is AI-ready and can run without AI or with optional AI.
MetisOne works standalone for corporate workflow setup and integrations, without ARX or AERIX. It can also connect to ARX and AERIX for private and hybrid AI.
Organisations select the modules they need and can add more over time. Deployment is on-premises or in the customer’s own private cloud.
A practical guide to choosing ERP modules around business work, with optional AI and room to expand.
Read the articleHow to frame ERP deployment decisions around ownership, administration, workflows and optional AI.
Read the articleDiscuss your operational priorities, deployment requirements and evaluation criteria with our team.