MiroxMirox
  • Platform

    • Philosophy
    • Platform Overview
    • Platform Resources
  • Mirox-Cloud

    • Cloud Overview
    • Connected Microservices
  • Mirox-Agent

    • Agent Overview
    • Deployment Options
    • Data Scraper
    • Digital Twin
  • Technical Details

    • Metric Collection
  • Information

    • Supported Plants
  • Plant Types

    • Solar Plants
    • Wind Plants
    • Battery Storage
  • Monitoring & Visualization

    • Real-time Monitoring
    • Digital Twin
    • Component States
    • Loss Detection
    • Efficiency Detection
    • KPI Dashboard
  • Data Management

    • Events
    • Tickets
    • Forecasts
    • Reports
  • Integration & Sharing

    • Cooperations
    • API Tokens
    • VPN
    • Proxy
  • AI

    • AI Assistant & Wizards
    • Agentic Access (MCP)
  • Billing

    • Market & Tariffs
    • Accounting & Billing
  • Collaboration

    • Invitations
  • Security

    • Authentication
    • Permission System
    • Cooperation Restrictions
    • Access Audit Logging
  • Nodes

    • mrxnode
  • Application

    • Door Control
    • Generic Relay
  • Edge Cluster

    • Orchestration
  • Getting Started

    • First Steps
  • Personal

    • Using the VPN
    • Using the Proxy
    • Two-Factor Authentication
    • Sessions
    • API Tokens
  • Per Park

    • Contacts
    • Network Devices
    • Data Loggers
    • Components
    • Direct VPN (per Agent)
  • Organization

    • Member Permissions
    • Cooperations
    • File Storage
  • Data Export

    • Export Metric API
    • MiroxQL Query Language
    • External Report Generation
    • Grafana
    • API Overview
  • Support

    • Request Integration Guide
  • mrxnode

    • Overview
    • How-To Guide
    • Container Deployment
    • Command Cheatsheet
    • Troubleshooting
  • Reporting

    • External Report Generator
  • English
  • Deutsch
  • Español
  • Français
  • Português
  • Italiano
  • English
  • Platform

    • Philosophy
    • Platform Overview
    • Platform Resources
  • Mirox-Cloud

    • Cloud Overview
    • Connected Microservices
  • Mirox-Agent

    • Agent Overview
    • Deployment Options
    • Data Scraper
    • Digital Twin
  • Technical Details

    • Metric Collection
  • Information

    • Supported Plants
  • Plant Types

    • Solar Plants
    • Wind Plants
    • Battery Storage
  • Monitoring & Visualization

    • Real-time Monitoring
    • Digital Twin
    • Component States
    • Loss Detection
    • Efficiency Detection
    • KPI Dashboard
  • Data Management

    • Events
    • Tickets
    • Forecasts
    • Reports
  • Integration & Sharing

    • Cooperations
    • API Tokens
    • VPN
    • Proxy
  • AI

    • AI Assistant & Wizards
    • Agentic Access (MCP)
  • Billing

    • Market & Tariffs
    • Accounting & Billing
  • Collaboration

    • Invitations
  • Security

    • Authentication
    • Permission System
    • Cooperation Restrictions
    • Access Audit Logging
  • Nodes

    • mrxnode
  • Application

    • Door Control
    • Generic Relay
  • Edge Cluster

    • Orchestration
  • Getting Started

    • First Steps
  • Personal

    • Using the VPN
    • Using the Proxy
    • Two-Factor Authentication
    • Sessions
    • API Tokens
  • Per Park

    • Contacts
    • Network Devices
    • Data Loggers
    • Components
    • Direct VPN (per Agent)
  • Organization

    • Member Permissions
    • Cooperations
    • File Storage
  • Data Export

    • Export Metric API
    • MiroxQL Query Language
    • External Report Generation
    • Grafana
    • API Overview
  • Support

    • Request Integration Guide
  • mrxnode

    • Overview
    • How-To Guide
    • Container Deployment
    • Command Cheatsheet
    • Troubleshooting
  • Reporting

    • External Report Generator
  • English
  • Deutsch
  • Español
  • Français
  • Português
  • Italiano
  • English
  • Getting Started

    • First Steps
  • Personal

    • Using the VPN
    • Using the Proxy
    • Setting Up Two-Factor Authentication
    • Managing Your Sessions
    • API Tokens
  • Per Park

    • Managing Plant Contacts
    • Managing Network Devices
    • Configuring Data Loggers
    • Configuring Components
    • Configuring VPN Servers per Agent (Direct VPN)
  • Organization

    • Managing Member Permissions
    • Creating Cooperations
    • Using File Storage
  • Data Export

    • Export Metric API
    • MiroxQL Query Language
    • External Report Generation
    • Using Grafana as an External Read Platform
    • API Overview
  • Support

    • Request Integration Guide
  • mrxnode

    • mrxnode Overview
    • mrxnode How-To Guide
    • Container Deployment
    • mrxnode Command Cheatsheet
    • Troubleshooting

Managing Plant Contacts

Keep the people and companies behind each plant — the operator, the technical manager, the grid operator, the project company — recorded right on the plant so anyone working on it knows who to call. Contacts live once in your organization directory and can be linked to as many plants as you like, so you never type the same details twice.

Plant contacts are reference details only. They are an address book attached to a plant; they do not grant anyone access to the platform. To give a person login access or rights on a plant, see Managing Member Permissions.

Open in Mirox

Contacts are managed on a plant's Core data page. Open the plant's Core data page directly. The page shows the linked contacts under the Directory tab and the grid operator / project company as key contact cards.

How Contacts Work

A contact is created once in your organization's directory and then linked to a plant with a role. Because the underlying contact record is shared, the same person or company can appear on several plants, and editing their phone number or email updates it everywhere it is linked.

There are two places to manage them, both reached from the plant's Core data page:

  • Contacts — the general directory for the plant: operators, technical managers and any other people you want on record.
  • Key Contacts — two dedicated single slots for the Grid Operator and the Project Company, the two companies most plants need to identify.

To reach either, open the plant's Core data page and select the Edit (pencil) action on the plant title to open Park Settings, then choose the Contacts or Key Contacts tab from the sidebar.

Contact Types

When you add a general contact you give it a type so it sorts and displays sensibly in the directory.

TypeUse it for
OperatorThe party operating the plant
Technical ManagerThe person responsible for technical management on site
OtherAnyone else — add a free-text Label (for example "Insurer" or "Security") to describe the role
Grid OperatorThe grid operator company — managed on the Key Contacts tab
Project CompanyThe project / development company — managed on the Key Contacts tab

Info

Grid Operator and Project Company are not offered in the general type selector because they each have a single dedicated slot on the Key Contacts tab. Everything else goes under Contacts.

Adding a Contact to a Plant

  1. Open the plant's Core data page and select Edit on the plant title to open Park Settings.
  2. Choose the Contacts tab, then select Add contact.
  3. Pick a Contact Type (Operator, Technical Manager, or Other). For Other, fill in the Label so the role is clear.
  4. To reuse an existing person, start typing in Search Existing Contacts and pick them from the list — their details fill in automatically. To create a brand-new contact, just fill in the fields directly.
  5. Complete the details you have: name, company, email, phone, mobile and address.
  6. Save. The contact now appears in the Directory for this plant.

Tips

Search first. If the person or company is already in your organization directory, link the existing entry instead of creating a duplicate — that keeps their contact details consistent across every plant they touch.

Setting the Key Contacts

The Grid Operator and Project Company are surfaced as their own cards on the Core data overview because they are the two companies you reference most. Each is a single slot.

  1. Open Park Settings and choose the Key Contacts tab.
  2. For the role you want to set, select Link contact.
  3. Search for an existing organization contact, or enter a new company's details. The role is fixed for this slot, so there is no type to choose.
  4. Save. The company now shows on the matching key-contact card.

To swap the company, select Change on that slot and link a different contact — the previous one is unlinked automatically. Select Remove to clear the slot.

Editing and Removing Contacts

  • Edit details — on the Contacts tab, open a contact and update its fields. Because the record is shared, the change applies to every plant the contact is linked to.
  • Remove from this plant — unlink a contact from the plant without deleting it from your organization directory; it stays available to link elsewhere.
  • Delete from the directory — while editing a contact you can delete it from the organization entirely, which removes it from every plant.

Warning

Removing a contact from a plant only breaks the link for that plant. Deleting a contact from the directory removes it everywhere it is linked — only do that when no plant should reference it again.

Reusing Contacts Across Plants

Because contacts belong to the organization, not to a single plant, building your directory once pays off across your whole portfolio:

  • The same maintenance company can be the Technical Manager on every plant it services.
  • A grid operator linked as a Key Contact on one plant can be linked to others without re-entering its details.
  • Updating an email or phone number once updates it on every plant that references the contact.

See Platform Resources for how organizations, portfolios and plants nest together and why a shared directory fits that structure.

Related Guides

  • Platform Resources — how organizations, portfolios and plants are organized
  • Using File Storage — the other thing you maintain on a plant's Core data
  • Managing Member Permissions — give a person actual access and rights, as opposed to a directory entry
  • Permission System — the organization and job roles that govern who can edit a plant
Next
Managing Network Devices
MIT Licensed | Copyright 2026 Mirox Verwaltungs GmbH