Invitations

Invitations are how people join Mirox and gain access to your organization and its resources. Three distinct invitation types cover three distinct scenarios — onboarding a brand-new customer, adding a teammate to your own organization, and sharing resources with a partner organization — so you can pick the right one for each collaboration.

Invitation Types Overview

Invitation Type	New User	Existing User with Organization
Platform	Creates Organization, Portfolio	-
Organization	Joins existing Organization	Leaving own Org to join other Organization
Cooperation	Creates Organization; accesses shared resources	Accepts cooperation to share resources between two Organizations

Platform Invitation

Platform invitations are the entry point for new customers to the Mirox platform.

Purpose

Onboard new customers who will manage their own organizations
Provide initial access to the Mirox platform
Start the customer journey for asset owners

Who Can Send

Mirox support team
Mirox sales representatives
Authorized system administrators

What Recipients Can Do

After accepting a platform invitation:

Create a personal account on Mirox
Create and manage their own organization
Create their first portfolio to organize assets
Add parks to the portfolio
Invite their own team members
Establish cooperations with other organizations

When to Use

Use platform invitations when:

A new company wants to use Mirox for their renewable energy assets
A potential customer has signed a contract and needs platform access
You're onboarding a new asset owner who will manage their own resources

Organization Invitation

Organization invitations allow existing organizations to add new members to their team.

Purpose

Expand your organization's user base
Add team members with specific roles
Delegate resource management to staff

Who Can Send

Organization administrators

Recipient Roles

When inviting a new member, you assign one of these organization roles:

Role	Description	Typical Use Case
Admin	Full organization management, including members, billing, and resource control	Business owners, account owners
Moderator	Resource management without full organizational control	Operations leads
Asset Manager (Technical)	Technical asset management — full park and component administration, including component and event deletion and full ticket handling	Technical asset managers
Asset Manager (Commercial)	Commercial asset management — park and portfolio management plus contract, billing, and reporting focus; cannot delete components or events, and can read and create tickets but not close them	Commercial asset managers
Member	Standard resource access based on assigned per-resource permissions	Staff members, analysts
External	Limited view-only access	Temporary collaborators, auditors

Technical vs. Commercial Asset Managers

The two manager roles are siblings: Asset Manager (Technical) focuses on operations and field work, while Asset Manager (Commercial) focuses on contracts, billing, and reporting. Neither can assign the other's role, and only Admins and Moderators can grant a manager role at all.

The role you assign sets each member's baseline access. Admins can refine it further by granting individual park or portfolio permissions on top of the org role. See Permission System for the full role model.

What Recipients Can Do

After accepting an organization invitation:

Access the organization's dashboard
View and interact with resources based on their role
Perform actions permitted by their assigned role
Cannot create their own organization (they join the existing one)

When to Use

Use organization invitations when:

Hiring new employees who need platform access
Adding contractors to your team temporarily
Granting access to consultants or advisors
Expanding your internal user base

Restrictions

Invited users become members of your organization
They cannot access resources outside your organization (unless through cooperations)
Their permissions are controlled by the organization administrators
Account remains tied to the organization

Onboarding Steps

One Organization Per User

A user can only be a member of one organization at a time. If you already belong to an organization and receive an invitation to another, you must leave your current organization first to accept.

If you need access to resources from both organizations, ask them to set up a Cooperation instead.

Step 1: Accept the Invitation

Click the invitation link in your email
You'll be directed to the registration page with pre-filled organization information

Step 2: Create Your Account (New Users Only)

If you don't have an existing Mirox account:

Complete the registration form with your personal details
Set a secure password
Verify your email address through the confirmation link

Step 3: Access Your Organization

After verification (or immediately for existing users), you're automatically added to the organization:

You receive the role assigned by your administrator (Admin, Moderator, Asset Manager (Technical), Asset Manager (Commercial), Member, or External)
Your permissions and resource access are configured by your organization
Navigate to your dashboard to see available resources

Tips

Your organization administrator controls your access level. If you need additional permissions, contact your organization's admin.

Cooperation Invitation

Cooperation invitations enable resource sharing between organizations while maintaining clear ownership boundaries. Unlike organization invitations, cooperation invitations allow the recipient to create their own organization.

Purpose

Share specific resources with external organizations
Enable collaboration without merging organizations
Provide controlled access to partners, investors, or service providers
Allow the recipient to maintain their own organizational identity

Who Can Send

Organization administrators of the resource-owning organization

Access Model

Administrator Access Only

Only administrators in the cooperating organization can access shared resources. Regular members, moderators, and guests of the partner organization cannot access cooperation resources.

This restriction ensures:

Clear accountability for shared resource access
Reduced risk of unauthorized data exposure
Simplified permission management between organizations

Permission Levels

When establishing a cooperation, you define the maximum permission level for the shared resources:

Note: each level inherits the permissions of the level beneath it.

Permission	Description	Typical Actions
Operator	Full operational access	Configure settings, manage components
Technical Manager	Technical management of the plant	Diagnostics, technical operations, monitoring
Asset Manager	Commercial-authority peer to the Technical Manager	Contracts, billing, and reporting tasks
Viewer	Read-only access	View data, generate reports
None	No access	Blocked from resource

Permission Delegation

The partner organization can only delegate permissions equal to or lower than the shared level:

Example: If Organization A shares a park with Organization B at the Technical Manager level:

Organization B admins can grant their members the Technical Manager permission
They can also grant Viewer
They cannot grant Operator permission (higher than the shared level)

What Recipients Can Do

For new users receiving a cooperation invitation:

Create a personal account on the Mirox platform
Create and manage their own organization
Access shared resources from the cooperating organization
Delegate permissions to their organization members (within cooperation limits)

For existing organizations receiving a cooperation invitation:

Organization admins can accept the cooperation
Access shared resources according to the cooperation agreement
Delegate permissions to their members (within limits)
Cannot modify ownership or core resource settings
Access can be revoked at any time by the resource owner

When to Use

Use cooperation invitations when:

Scenario	Example
Service Provider Access	Maintenance company needs monitoring access
Investor Reporting	Financial stakeholder needs performance data
Technical Support	External technicians need diagnostic access
Regulatory Compliance	Auditors need view access for verification
Asset Management	Third-party managers operate on your behalf

Restrictions

Partner organization admins only (not regular members)
Cannot exceed the shared permission level
Resource ownership remains with the original organization
All actions are logged and auditable
Access can be time-limited or revoked

Onboarding Steps (New User)

Step 1: Accept the Invitation

Click the invitation link in your email
You'll be directed to the registration page with information about the cooperation

Step 2: Create Your Account

Complete the registration form with your personal details
Set a secure password
Verify your email address through the confirmation link

Step 3: Create Your Organization

After account creation, you'll need to set up your own organization:

Enter your organization details:
- Organization name
- Contact information
- Business details
You automatically become the organization administrator

Step 4: Access Shared Resources

Once your organization is created, the cooperation becomes active:

You can access the resources shared by the partner organization
Your access level is defined by the cooperation agreement
Only administrators in your organization can access cooperation resources

Administrator Access Only

Cooperation resources are only accessible to organization administrators. If you need to grant access to your team members, you must delegate permissions within the limits set by the cooperation agreement.

For more details on cooperation permissions, see Cooperation Restrictions.

Onboarding Steps (Existing User with Organization)

If your organization receives a cooperation invitation:

An administrator from your organization must accept the cooperation
The cooperation is linked to your existing organization
Shared resources become accessible to your organization's administrators

For more details on managing cooperations, see Cooperations.

Comparison Summary

Aspect	Platform	Organization	Cooperation
Creates new organization	Yes	No	Yes
Creates portfolio	Yes	No	No
Joins existing organization	No	Yes	No
Resource ownership	Own	Shared within org	Own + access to shared
Permission source	Self-managed	Org admin assigned	Self-managed + cooperation agreement
User independence	High	Low	High
Typical recipient	New customers	Team members	External partners

Important Limitations

One Organization Per User

A user can only be a member of one organization at a time. This means:

You cannot join multiple organizations simultaneously
You cannot switch between organizations without leaving your current one
Organization invitations cannot be accepted if you're already a member of another organization

If you need to work with multiple organizations, use cooperations to share resources between them instead.

Best Practices

For Platform Invitations

Reserve for genuine new customers who will own assets
Ensure contract and onboarding preparation is complete
Provide follow-up support for organization and portfolio setup

For Organization Invitations

Assign the minimum role necessary for the user's function
Review and update roles periodically
Remove access promptly when no longer needed

For Cooperation Invitations

Share at the lowest permission level that meets requirements
Set expiration dates for temporary collaborations
Regularly audit cooperation access and activities
Document the purpose of each cooperation

Cooperations — set up and manage cross-organization resource sharing
Permission System — the full organization-role and job-role model behind every invitation
Cooperation Restrictions — how a shared permission level caps what a partner can delegate
First Steps — onboarding checklist for a new organization