Help Center
Roadmap
Changelog

Have something to say?

Tell us how we could make the product more useful to you.

Let user select date from which Absolute Impact is calculated

I want the possibility to set my date from which the absolute impact is being calculated. As an example, I take Warmte sanitair water (thermal energy) from building Compostela. Change detected on 6/02/2026 at 4:00 Manager has modified some setting on February 21st. Not enough to trigger a change detection apparently, but looking at the data you clearly see a difference (not very scientific, I know). I’m actually pretty surprised this isn’t flagged as a change. It’s still an over consumption, but there’s a change there. I would like to to see the impact from February 21st on.

Jonathan Fronhoffs about 1 month ago

💡

Feature Requests

Advanced user management (invites, password reset, user actions)

Summary Add traditional SaaS-grade user management capabilities so admins can view invite status, resend invites, reset passwords, deactivate users, and perform other lifecycle actions from the admin panel. Problem statement Admins currently lack visibility into the state of sent invitations and have no self-serve tools to take action on users (resend invites, force password resets, deactivate accounts, etc.), forcing them to contact support or work around the product for routine user management tasks. 🚦 Definition of ready Before entering a cycle, confirm: [ ] Problem statement is clear [ ] Acceptance criteria are defined [ ] Scope & non-goals are explicit [ ] Linked to relevant context [ ] Can be completed by one person in one sprint If any box is unchecked → do not pull into sprint Acceptance criteria [ ] Admins can see a list of all pending invitations, including invitee email, invite date, and expiry status [ ] Admins can resend an expired or pending invitation from the UI [ ] Admins can revoke a pending invitation before it is accepted [ ] Admins can trigger a password reset email for any active user [ ] Admins can deactivate (suspend) a user, immediately revoking their access without deleting their data [ ] Admins can reactivate a previously deactivated user [ ] Admins can change a user's role (e.g. member → admin) from the user management table [ ] Admins can remove a user from the workspace entirely [ ] All user management actions are logged in an audit trail visible to admins If this checklist is complete, the issue is done. Scope In scope Pending invitations table with status, sent date, expiry, and per-invite actions (resend, revoke) Password reset trigger (sends reset email to user) User deactivation / reactivation Role change from user table User removal from workspace Audit log entries for all of the above actions Out of scope SSO / SAML provisioning and deprovisioning Bulk user import / CSV upload Fine-grained permission sets beyond existing role types User impersonation / "log in as user" Self-serve account deletion by end users Context & links [ ] Fathom (customer feedback): [ ] PRD / Project: [ ] Incident: [ ] Design: [ ] Technical decision record: Implementation notes (optional) Invitation state should cover: pending, accepted, expired, revoked Deactivation should invalidate active sessions immediately (consider token invalidation strategy) Password reset should reuse the existing reset flow; this is just an admin-triggered entry point Audit log can be appended to an existing audit trail if one exists, or scoped as a new lightweight table ✅ Definition of done [ ] Acceptance criteria are met [ ] Code is reviewed & merged [ ] Tests pass (functional + design where applicable) [ ] Feature is deployed [ ] Docs / release notes updated if needed

Linear about 2 months ago

💡

Feature Requests

Monthly Report: Non-Consumption Metrics (Temperature, CO2, etc.)

Feature Request Overview Extend the monthly report to include non-consumption meter data such as average temperature, CO2 levels, and other environmental sensors, giving users a more complete picture of their building's performance. Problem The current monthly report focuses on consumption data (electricity, gas, water). Non-consumption metrics such as indoor temperature and CO2 concentration are not included, even though many users have these sensors connected. Administrators miss out on key comfort and air quality insights in their regular reporting. Proposed Solution Add a non-consumption metrics section to the monthly report covering connected environmental sensors. Metrics to include (where available): average, min, and max temperature (°C), average CO2 levels (ppm), and other relevant sensor types (e.g. humidity). Data presented per sensor or zone/building level, consistent with the existing report structure. Optionally flag periods where values exceeded comfort or regulatory thresholds (e.g. CO2 above 1000 ppm). User Story As an administrator, I want the monthly report to include non-consumption metrics such as average temperature and CO2 levels, so that I have a complete overview of both energy use and environmental conditions in my buildings. Value Provides a holistic view of building performance beyond energy consumption Supports indoor air quality and comfort monitoring at a glance Adds value for customers with environmental sensors already connected to the platform

Linear about 2 months ago

💡

Feature Requests

Monthly Report: Data Quality Metrics

Feature Request Overview Extend the monthly report with a data quality section that gives administrators insight into the reliability and completeness of meter data — highlighting meters that have stopped sending data or have gaps in measurements. Problem The monthly report does not surface any information about data quality. Users have no way of knowing from the report whether a meter is still actively sending data, or whether readings have been missing. This can lead to silent data gaps going unnoticed. Proposed Solution A dedicated data quality section in the monthly report summarising the status of all meters over the reporting period. Metrics to include: last received data timestamp per meter, percentage of expected readings received (completeness), meters flagged as inactive or with missing data, and duration of any data gaps. Visual indicators (e.g. green/orange/red) per meter to make quality issues immediately visible. User Story As an administrator, I want the monthly report to include data quality metrics per meter, so that I can quickly identify meters that have stopped sending data or have significant measurement gaps and take corrective action. Value Prevents silent data gaps from going unnoticed Improves trust in the data presented in reports Helps administrators proactively manage meter health and maintenance

Linear about 2 months ago

💡

Feature Requests

Later

Static Threshold Alerting for All Meter Types

Feature Request Overview Allow users and administrators to configure static threshold-based alerts for all meter types on the platform — covering both consumption meters (e.g. water, electricity, gas in volume/energy units) and non-consumption meters (e.g. CO2 in ppm, temperature, humidity). Problem Currently, alerting is limited to anomaly detection based on dynamic/statistical analysis. There is no way to set a fixed threshold and receive an alert when a meter reading crosses that value. This is a common need for both operational monitoring (e.g. "alert me when water consumption exceeds X m³") and environmental/comfort monitoring (e.g. "alert me when CO2 exceeds 1000 ppm"). Proposed Solution Static threshold configuration — Allow users to define upper and/or lower threshold values for any meter, regardless of type. Support for all meter types — Including but not limited to: Consumption meters: water (m³), electricity (kWh), gas (m³) Non-consumption meters: CO2 (ppm), temperature (°C), humidity (%), pressure, etc. Alert triggers — Send a notification (email and/or in-app) when a reading crosses the defined threshold. Threshold management — Administrators can view, edit, and delete configured thresholds per meter or per building/zone. Optional: sustained breach alerts — Only trigger an alert if the threshold is exceeded for a configurable duration, to avoid noise from short spikes. User Story As an administrator, I want to set static threshold values on any meter type so that I am alerted when readings exceed or fall below a defined limit, enabling proactive monitoring beyond anomaly detection. Value Enables proactive operational and environmental monitoring Covers use cases that dynamic anomaly detection cannot address (e.g. regulatory limits, comfort thresholds) Applicable across a wide range of industries and meter types Gives users direct control over alert sensitivity

Linear about 2 months ago

💡

Feature Requests

Email Send History per User

Feature Request Overview Allow administrators to view a log of all emails the platform has sent to each user, so they can track what information has been communicated and audit notification history. Problem There is currently no way to view which emails have been sent to a specific user. This makes it difficult to audit communication history, troubleshoot missing notifications, or verify that users have received important information. Proposed Solution Per-user email log — A view (e.g. in the user detail page) listing all emails sent to that user, including the email type, subject, timestamp, and delivery status. Filterable & searchable — Allow filtering by email type (anomaly alert, report, system notification, etc.) and date range. Platform-wide overview (optional enhancement) — An aggregate view showing email activity across all users, useful for auditing and support. User Story As an administrator, I want to see a history of all emails sent to each user by the platform, so that I can track what information has been communicated and verify that users are receiving the right notifications. Value Improves transparency and auditability of platform communications Helps administrators troubleshoot cases where users claim not to have received notifications Supports compliance and reporting needs around information delivery

Linear about 2 months ago

💡

Feature Requests

Customizable Anomaly Alert Email Content & Attachments

Feature Request Customer: Enersee Overview Allow administrators to customize the content of anomaly alert emails and attach custom files (e.g. guidance documents, resolution steps). This empowers companies to tailor notifications to their internal processes and provide contextual, actionable information directly within the alert. Problem Currently, anomaly alert emails have a fixed format and content. Administrators have no way to add company-specific guidance or resolution steps to these notifications, which means recipients need to look elsewhere for context on how to handle each anomaly type. Proposed Solution Custom email body editor: Let administrators edit the text content of anomaly alert emails from the settings panel (e.g. rich text or template-based editor with dynamic variables). Custom attachments: Allow administrators to upload one or more files (PDF, DOCX, etc.) that are automatically appended to anomaly alert emails — e.g. a company-specific troubleshooting guide or standard operating procedure. Per-anomaly-type customization: Optionally, support different templates/attachments per anomaly type or severity level. User Story As an administrator, I want to customize the content and attachments of anomaly alert emails so that recipients receive company-tailored guidance and resolution steps alongside the alert, reducing response time and improving handling consistency. Value Reduces time-to-resolution for anomalies by providing in-email guidance Allows companies to embed SOPs, checklists, or escalation contacts Increases the perceived value and actionability of alerts for end users

Linear about 2 months ago

💡

Feature Requests

In Progress

Visualise incoming data flow

Full visualisation of the data flow, including mandates and expiry dates. This should give the customer visibility on how much data is already in the system, which buildings are connected and where data is still missing. ​ IR-0012 IR-0017 IR-0028 IR-0040 IR-0041 IR-0080 IR-0087 IR-0095 IR-0096

Arnor Van Leemputten about 2 months ago

💡

Feature Requests