MGS v1.3.0
MGS v1.3.0 introduces Organization co-owners, letting a tenant admin account be owned and managed by multiple people rather than a single individual.
New Features & Enhancements
Organization Co-Owners for Tenant Admins
Your tenant admin account is now an Organization that can have more than one equal co-owner. Previously, everything a tenant admin managed, including tenants, users, and the subscription, belonged to a single person. If that person left the company or lost access, recovering the account meant going through Climission support. Co-owners remove that single point of failure and let a team share ownership fully.
A new Access Control page. Tenant admins have a new Access Control area for managing their organization in one place: who the co-owners are, inviting new ones, and the company name shown on billing and subscription forms.
Invite an equal co-owner by email. A tenant admin can invite another person to co-own the organization. The invitation is confirmed through a verification email, and once accepted the new co-owner has the same full rights, including managing tenants, members, billing, and the subscription itself. There is no primary owner, all co-owners are equal.
Billing and subscriptions belong to the organization. The plan, subscription requests, and billing details are now keyed to the organization rather than to one user, and every tenant in the organization counts against the organization's plan. Subscription and request forms show the organization's company name, and the Climission admin grids for subscriptions and requests are organized the same way.
Everyone stays informed. Subscription and account lifecycle emails, such as plan changes and limit warnings, are now sent to all co-owners so no notification depends on a single inbox.
Nothing changes for existing accounts. Every existing tenant admin is automatically set up as the sole co-owner of their own organization, with the same tenants, subscription, and access they had before. There is nothing to configure, and existing tenant operators and delegated users continue to work exactly as they do today.
This gives organizations a built-in way to spread account ownership across a team and keep control of their tenants and billing even as people join or leave.
Platform Stability
Auto-Recording Policies Can Save Steps to IPFS Again
Policies configured to automatically record and upload each step to IPFS could fail to upload, because the recording process did not carry the tenant's context and the platform could not locate that tenant's IPFS settings. The recording now carries the correct tenant context through to each upload, so auto-recorded steps are stored to IPFS reliably. Regular IPFS publishing was not affected, and no policy configuration changes are required.
For the full changelog and release notes on the open-source Guardian please visit: https://github.com/hashgraph/guardian/releases
Last updated