Who sees what, where the platform runs, and whose servers it can run on
These are the three questions an IT department asks before it looks at a single consumption curve. This page answers them with what the code carries, and stops where the code stops — including where the next sentence would have sold better.
Who sees what, and who decides?
You do. Access rights are held by your own administrator, inside the product, with no involvement from Softee — no ticket, no lead time, no billable intervention to change what a role is allowed to do.
The product first separates usage into three distinct workspaces, entered according to your role.
Viewing
The workspace for people who read: estate summary, dashboards, indicators. This is the one you open to an operator, a director, a site contact.
Management
The workspace for people who act: configuring the estate, the indicators, the alerts, the exports. This is the energy manager’s desk.
Administration
The workspace for people who decide: reference lists, organisation settings and the rights matrix. Everything this section describes is set here.
Inside that split, a rights matrix crosses three business roles — manager, supervisor, user — with a catalogue of 18 features. Each cell is switched on or off, at the level of a whole workspace or of one feature. A regional supervisor who must see invoices without editing the estate is a combination of cells, not a change request.
That setting is enforced in the interface too, not only underneath it: a feature a role may not use is hidden and blocked, and the user is redirected to the first feature they can reach instead of landing on an empty page. It is an operational detail, and it is the one that separates access rights that hold from access rights you get around by knowing the URL.
Where does the platform run?
In France. That is where the Softee platform is hosted.
Where that sentence comes from, and what it does not say. No code repository proves a location: a location is not in a source file. So this comes from the company rather than from a line of code, and we would rather tell you that than let it pass for a technical property.
Its scope is narrow, deliberately. It concerns where the platform is hosted. We do not stretch it to cover every processing operation, and we draw no regulatory compliance claim from it: a hosting location is not a compliance statement, and it is worth asking any vendor who offers you one as the other to make the same distinction.
Can it be installed on your own servers?
Yes. Installation on a server you own is possible, and it is covered by a documented procedure — including the case of a server with no internet access, where the components are transferred as an archive and normal operation requires no outbound traffic.
This is often the deciding point for a public-sector buyer: it lets the case be built on your own infrastructure, with your filtering rules and your operations team, rather than on ours.
The reserve is part of the sentence. What exists is an installation procedure — dated, written — and the delivery chain that makes it possible. It is not an accreditation, not a label, not a listing on an approved-supplier register: we announce none of those, and the installation document attests none of them either.
If your process requires one, raise it in the first conversation. Discovering it at the end of an evaluation helps nobody.
In French and in English
The interface exists in both languages, and the two translation catalogues are at parity — the same number of keys on each side. In practice: a user who switches to English does not hit labels left in French in the middle of a screen, which is the usual way an "English version" turns out to be partial.
How do you ask for help?
From inside the product. A support ticket is raised in the application, with a severity level and an attachment; the exchange then continues as comments and the ticket status is tracked. The request stays attached to your organisation rather than scattered across individual mailboxes.
Frequently asked questions about access rights and deployment
Let us work through your requirements before the demonstration
Send your requirements as they are written — roles to separate, hosting, installation on your infrastructure, documents expected. We will tell you what the product covers, what it does not, and what would take a contractual commitment rather than a capability.