Roles, permissions and security
Separate data entry, review and approval across roles, with single sign-on through your Microsoft identity and a log of what users do.
Metal accounting figures can end up in financial statements and board reports, so who can enter, change and approve them matters. Unless it is carefully protected, a shared spreadsheet lets anyone who can open it change any number, including the formulas. MAX separates those duties and records who did what.
Roles that match how your site works
Access in MAX is granted through roles. A role can allow or deny reading, creating, editing and deleting each type of record, and can go further: down to particular records, individual fields, and the menu items a user sees. MAX ships with roles for administrators, general users, data entry only and read only access, and sites add their own.
For example, a site can separate the people who enter shift data, the metallurgists who review and adjust it, and the managers who approve reports, so that no one person can enter a value, change the formula that uses it and approve the result. Report approval records the approving user and time, and only users with the right permission can approve or revert a report.
Sign in with your Microsoft account
MAX uses Microsoft Entra ID (formerly Azure AD) for single sign-on, so users sign in with the same account they use for email and Teams, and leave access with that account when they leave the company. Multi-factor authentication, conditional access and password policies come from your own Entra ID configuration, so MAX follows the rules your IT team already enforces.
Groups in Active Directory or Entra ID can be mapped to MAX roles, so access is managed where your IT team already manages it. Sites running MAX on their own network can also use Windows authentication, and MAX supports its own password sign-in with account lockout where neither is available. The MAX web API accepts Entra ID tokens for integrations.
A record of what users do
MAX keeps a user activity log of sign-ins, commands run, records created and deleted, and changes to values with their previous and new values. What is logged, and for how long, can be set per type of data, and logging of record reads can be switched on where a site needs it. A separate system log records errors and warnings, which helps Nutava support diagnose a problem quickly. Together with the per-value history described under one auditable source of truth, this gives auditors the trail they ask for.
Protected in transit and at rest
MAX is served only over HTTPS, with HTTP Strict Transport Security, and connections to FTP servers, email servers and the database can use TLS. When Nutava hosts MAX, each customer has its own Azure App Service and Azure SQL database in Australia; Azure SQL encrypts data at rest by default, and backups are geo-redundant. Sites that host MAX themselves keep full control of their own infrastructure, encryption and backups.
Designed for governance
Segregation of duties, controlled access and audit trails are part of what the AMIRA P754 code asks of a metal accounting system.
More MAX4METS features
- One auditable source of truth
- Capture data from every source
- Transparent formula management
- Metal balance and reconciliation
- Downtime and delay accounting
- Shift, daily, weekly and monthly reporting
- Bullion, concentrate and product tracking
- Site map and plant model
- Approvals, period locking and tasks
Ready to elevate your metallurgical accounting?
Book a demonstration and see how MAX fits your plant, your data sources and your reporting cycle.