Creating Cooperations

A cooperation lets you share specific plants and portfolios with another organization — a service provider, asset manager, or investor — so they can work in your assets from their own account while you keep full ownership and control. This guide walks you through inviting a partner, sharing resources at a capped role, and managing the relationship over time.

For the concept behind cooperations (reference-based sharing, the two access layers, security guarantees), see the Cooperations feature. This page is the how-to.

Before You Start

Only an organization Admin can invite, accept, or manage a cooperation. If you do not see the Invite Cooperation button, you do not hold the right organization role.
You can only share resources your organization owns. You cannot re-share a plant that came to you through another cooperation.
Decide which plants or portfolios you want to share and at what level before you invite — you can always adjust later.

Open the Cooperations Tab

All cooperation management lives on your Organization page.

Open your Organization page and select the Cooperations tab (in the app: Profile menu ▸ your organization ▸ Cooperations).
You will see two lists: Outgoing Cooperations (partners you invited) and Incoming Cooperations (partners who invited you). Use the search box to filter by partner name.

Open in Mirox

Open the Cooperations tab — the link resolves to your default organization.

Invite a Cooperation

On the Cooperations tab, click Invite Cooperation.
Enter the email address of a person at the partner organization, and choose the language for the invitation email.
Click Send Invitation.

What happens next depends on the recipient:

The email belongs to an existing organization — Mirox recognises it and asks you to confirm. Click Create Cooperation to establish the link directly. Every Admin of that organization is notified, and the cooperation activates as soon as one of them accepts.
The email is new to Mirox — an invitation is sent that guides the recipient to register, create their organization, and join the cooperation. Until they finish, the cooperation shows the invited email address as its label and sits in an Invited state.

Warning

You cannot create a cooperation with your own organization. If the email belongs to a member of your own organization, Mirox blocks the request and tells you so.

After the invitation is sent, the Manage Permissions dialog opens automatically so you can start sharing resources straight away.

Sharing is how the partner actually gains access. You grant a single job role on each shared resource, and that role becomes the ceiling for everything the partner can do with it.

Open the cooperation's actions menu (the three-dot icon on its card) and choose Edit Permissions — or use the dialog that opened right after inviting.
Choose a Resource Type: Portfolio or Park (plant).
Pick the specific portfolio or plant you want to share.
Choose the Role the partner receives on it.
Optionally set an Expiration date for this individual share so access lapses on its own.
Click Add Permission.

Repeat to share more resources. Each share appears under Current Permissions, where you can change its expiration or remove it with the trash icon.

A cooperation never carries an organization's highest authority across the boundary. The roles available for sharing are:

Shared role	What the partner can do with the resource
Viewer	Read-only visibility into the plant and its data
Technical Manager	Technical operations work on the plant
Asset Manager	Commercial-authority work on the plant

The Operator role is reserved for resources your organization owns directly and can never be shared through a cooperation. When you share a resource you only received through another cooperation, the only role you can pass on is the one you were given (or Viewer) — never higher.

How Far a Shared Role Travels (the Delegation Limit)

The role you share is a hard ceiling. On the receiving side, only the partner's Admin can reach the shared resource, and they may hand it to their own members only as Viewer or the role you shared — nothing higher, nothing in between.

So if you share a plant at Technical Manager, the partner's members can end up with at most Technical Manager; if you share at Viewer, they stay read-only no matter how the partner manages their team. The exact rules are spelled out in Cooperation Permission Restrictions.

Tips

Because the shared role caps every downstream grant, handing a partner Viewer can never quietly become edit access later. If you lower a shared role or remove a share, the partner's members lose access accordingly.

Manage a Live Cooperation

Only the organization that initiated the cooperation controls its lifecycle. From the actions menu on the cooperation's card you can:

Edit Expiration — set or clear an expiration date for the whole cooperation. When it passes, all access through the relationship ends automatically.
Pause Cooperation — block all access through the relationship without deleting it. Use this to suspend a partner temporarily.
Resume Cooperation — re-enable a paused cooperation. Resume stays available even while paused.
Resend Invitation — send the invitation email again to a partner who has not yet accepted.
Remove Cooperation — end the relationship entirely. The partner immediately loses access to everything you shared.

Click a cooperation's card to open its details drawer, which shows the current status (Active, Invited, Pending, or Paused), the contacts on each side, the expiration date, and every resource you have shared.

Info

On an Incoming cooperation you do not control the shared resources — the other organization owns them. You will not see permission, expiration, or pause controls for cooperations that were shared with you.

Cooperations — the concept, security model, and use cases behind cross-organization sharing
Cooperation Permission Restrictions — exactly how a shared role caps what a partner can delegate
Managing Member Permissions — invite members and grant job roles inside your own organization
Permission System — the organization and job roles cooperations build on
Audit Log — the record of access made through a cooperation