Report templates and chapters, My Metrics and Data Export templates, and the alert rules, receivers, or message templates in the Alarm Manager can be marked private. A private item is visible and usable to every member, with only its creator, an admin, or a moderator able to edit or delete it.
A contact's certificates are uploaded through a wizard in the organization and attached to the contact. The assistant reads each document's type, validity scope and expiry during the upload.
A "Client" role below "Viewer" now appears in a plant's grant dialogs for the plant's customer, with an "Access until" expiry. It has access to live and historical operating data — production, battery, turbines, analysis, forecast and market prices — but not events, tickets, reports, exports, files, network or money figures, or plant push notifications.
Member management and cooperation changes in the organization are now handled by the moderator role alongside the admin: inviting and removing members, changing their roles, joining and removing a cooperation, and changing its shared permissions. The technical asset manager role still sees the team but no longer manages it.
A file or folder from a plant or an organization can now be sent to someone outside it, who opens it with a link plus a 6-digit code or a set password, within chosen expiry, visit and download limits. A "Shares" tab now lists every share and what each visitor did.
Every network of a plant can now be tagged by what it carries — "Plant control", "Network infrastructure", "Cameras" or "Security systems" — when it is added, edited or opened for remote access. The new "Security Officer" role reaches only the networking, camera and security networks, never production, revenue or plant control.
The "Sites" tab now lists, under "Shared with your organization", the plants and portfolios other organizations share, below the organization's own. Each row names who shared it, the role given, the portfolio a plant comes through, and reads "visible only — no data access" when it cannot be opened.
A plant can now be moved into another portfolio of the same organization with "Move to portfolio" in the organization's plant list. Members and partner organizations who reach the source portfolio lose the plant, those who reach the target gain it, and access granted on the plant itself is kept.
A notice is sent seven days before an API token expires, another when it expires, and one more when an application still uses it afterwards. Each notice names the token and points to the profile's "API Tokens" tab, where "Rotate API Token" issues a new secret.
An invitation to another organization can now be accepted from the profile while the account still belongs to one. Accepting first removes the account from its current organization, and where the account is that organization's last admin, the organization is deleted with its portfolios and plants after typing DELETE to confirm.
"Rotate" in a token's menu under "API Tokens" on the profile page now gives an existing token a new secret value, keeping its name, description and permission level with a newly chosen expiry. The old value stops working immediately.
A member's access can now carry an end date, renewable later from the list, and each permission for a plant or portfolio can have its own end date. A paused member keeps their place in the organization but cannot do anything until resumed.
The profile page is now split into "General", "Security" and "API Tokens". Under "Security" every place the account is signed in is listed, with browser, operating system, city and country, IP address and last activity, and one click ends every other session.
"API Tokens" in the profile now offers an "LLM (AI)" token, which serves as the key in any OpenAI-compatible tool or library to reach Mirox's AI features. The token gives access to nothing else in the account.