Cooperations

Cooperations let your organization share specific parks and portfolios with another organization across the organizational boundary — so a service provider, asset manager, or investor can work in your plants without ever leaving their own account, and you keep full ownership and control.

Cooperation Concept

A cooperation is a formal link between exactly two organizations. The organization that owns a resource shares a reference to it — never a copy of the data — and decides which job role the partner organization receives on that resource. Nothing is shared until both sides agree, and the owning organization can adjust, pause, or end the relationship at any time.

Two ideas sit at the centre of the model:

The owner stays in control. Only the organization that owns a park or portfolio can share it, change the shared role, or revoke it. The partner organization can never re-share what it received with a third organization.
Two layers of access. First, your organization decides what role it shares with the partner. Second, the partner organization decides which of its own members may reach the shared resource — but it can never grant more than it was given. This cap is the core of cooperation restrictions.

Establishing a Cooperation

A cooperation always starts with an invitation, and only an organization Admin can send or accept one.

Inviting an Existing Organization

If the partner already has a Mirox organization, you invite it by its organization identifier. Every Admin of the target organization receives an email, and the cooperation activates as soon as any one of them accepts.

Inviting a New Partner by Email

If the partner does not have an organization yet, you invite them by email address instead. Mirox creates a lightweight placeholder organization to hold the pending relationship and sends the right onboarding email:

A brand-new contact is guided to register, create their organization, and join the cooperation in one step.
An existing user who is not yet in any organization is guided to create their organization and accept.
A user who already belongs to an organization is asked to accept from that organization instead.

Info

The placeholder organization is just a stand-in for the pending invitation. If the invite is declined, it is removed automatically along with the pending cooperation. The invited email address is shown as the label until the partner finishes joining.

Once the cooperation is active, the resource owner chooses which parks and portfolios to share and which job role the partner receives on each one. You can add or remove shared resources and change the granted role at any time, and you can attach an expiration date to any individual share.

Managing a Live Cooperation

After a cooperation is established, the initiating organization owns its lifecycle and can:

Pause and resume the cooperation. Pausing blocks all access through the relationship without deleting it, so you can suspend a partner temporarily and re-enable them later.
Set or clear an expiration date for the whole cooperation, after which access ends automatically.
Remove the cooperation entirely when it is no longer needed.

Initiator-Only Controls

Pause, resume, and expiration of the cooperation as a whole can only be performed by the organization that initiated it. The partner organization can manage its own members' access, but cannot pause or expire the cooperation itself.

Access Control in Cooperations

What Your Organization Shares

When you share a park or portfolio, you grant the partner organization a single job role on it. That role becomes the ceiling for everything the partner can do with the resource.

Shared role	What the partner organization can do
Viewer	Read-only visibility into the resource and its data
Technical Manager	Technical operations work on the resource

For a cooperation-shared resource, the only roles a partner can pass on to its own members are Viewer and the role it was granted. Higher roles such as Operator are never available across a cooperation boundary.

How the Partner Grants Access to Its Members

On the receiving side, only the partner organization's Admin can reach a cooperation-shared resource and delegate it onward. Admins may assign their own members the Viewer role or the shared role itself, capped by what your organization granted. Members below Admin in the partner organization cannot pick up shared resources automatically — the relationship is deliberately narrow.

Tips

Because the shared role caps every downstream grant, you can be confident that handing a partner the Viewer role can never become edit access later — no matter how the partner manages its own team.

Member Lifecycle and Expiration

The same controls that keep a cooperation tidy also apply to the people inside your own organization, which matters when external collaborators join as members:

Pause and resume a membership to block a member's access without removing their record, then re-enable them later.
Set or clear a member's expiration date so their access ends automatically on a chosen day.

These act at the organization level and complement per-resource shares and cooperation expiration, giving you several independent ways to time-box access.

Use Cases

Cooperations support the common ways renewable energy assets are shared:

Service providers — maintenance, monitoring, and technical asset management firms working in your plants.
Financial stakeholders — investors, lenders, and insurers who need performance visibility but no operational control.
Multi-party projects — joint ventures and portfolio investments where several organizations need scoped access to the same assets.

Security and Compliance

Reference-based sharing. Partners see a live reference to your resources, never a duplicated dataset, so there is one source of truth.
Owner-only sharing. Only the resource owner can grant, change, or revoke a share; partners cannot re-share onward.
Capped delegation. What you share strictly limits what the partner can delegate internally.
Time-boxed access. Expiration on the cooperation, on individual shares, and on memberships lets access lapse on its own.
Auditable activity. Access through cooperations is recorded; see the Audit Log for the full record of who reached what.

Permission System — the organization and job roles that cooperations build on
Cooperation Restrictions — exactly how a shared role caps what a partner can delegate
Invitations — how organization, cooperation, and platform invites work together
Audit Log — the record of access made through cooperations
Reports — share performance reporting with external stakeholders