Orchestrav2 is the extranet portal developed by EGI, used by many property management firms and property administration companies to provide access to co-owners, landlord owners, and tenants to their management documents. Access to this secure space relies on a precise mechanism that begins well before the login screen. For property administrators, the ease of access depends less on the interface itself than on the configuration done upstream in the business software.
Back-office configuration: what conditions access to Orchestrav2
The Orchestrav2 login pages display a standard form with username and password. What this interface does not show is that access depends on prior configuration in the EGI business software. As long as the user profile is not correctly created on the back-office side, no connection is possible, even with the correct credentials.
The firm or its IT service provider must first create a user profile associated with the correct portfolio of co-properties or rental lots. This step involves several checks:
- The attachment of the profile to the firm and the relevant co-properties or mandates; otherwise, the user will not see any documents after logging in.
- The registration of a valid email address synchronized with the extranet module, which is a condition for receiving first connection instructions.
- The assignment of access rights appropriate to the role (administrator, manager, accountant), which determines which documents and features will be visible.
A property administrator managing multiple buildings has every interest in verifying that each lot or co-property is indeed associated with their profile. Omissions at this stage explain the majority of the blockages reported during the first connection.
To connect to the Orchestrav2 syndic portal, it is therefore necessary for this configuration chain to be complete, from the business software to synchronization with the extranet.
First connection and password recovery on Orchestrav2
The Orchestrav2 login screen includes a “First connection or forgot password” link that triggers the sending of a reset email. This mechanism only works if the email address registered in the back-office is correct and accessible.
The username and password are case-sensitive (uppercase and lowercase). This is a frequent source of errors. A username entered in lowercase when it was created with an initial uppercase letter will be rejected without an explicit message regarding the nature of the problem.
What to do when the reset link does not work
Several situations can block the procedure. The reset email may arrive in the spam folder, especially on professional email accounts with strict anti-spam filters. If no email arrives after several attempts, the problem is usually related to the address registered in the user profile.
In this case, only the firm (or the IT service provider administering the EGI instance) can correct the email address in the back-office. A user cannot modify their contact address from the Orchestrav2 portal. This point distinguishes Orchestrav2 from more recent real estate portals that offer autonomous profile management.
Accessible documents and limitations of the Orchestrav2 syndic portal
Orchestrav2 provides documents in accordance with the obligations arising from the ALUR law. For co-owners, the extranet provides access to account status, calls for funds, charge distributions, and general assembly minutes. For tenants, payment notices and documents related to the occupied housing are available for consultation.
The portal also allows for the dematerialization of mailings. An email notifies the recipient when a new document is available, reducing paper exchanges. Management reports and expense statements are archived and can be consulted at any time.
What the portal does not cover
Orchestrav2 remains a consultation and payment tool (provisions for charges, rents). It does not offer integrated messaging between co-owners and managers, nor does it provide work tracking or incident reporting. Firms that want these features must manage them through other tools or complementary solutions.
Field feedback varies on the ease of use of the mobile interface. The portal has a mobile version accessible from a browser, but it is not a downloadable native application. The ergonomics on smartphones depend on the browser used and the screen size.
Data security and GDPR compliance on Orchestrav2
The Orchestrav2 portal displays a detailed mention of the purpose of processing the collected data. The information is processed to ensure the publication of data in the secure extranet and for the electronic payment of rents or charge provisions.
The data controller is the property management firm, not EGI as the software publisher. This distinction has practical consequences: requests for access, rectification, or deletion of data must be addressed to the firm, which is the only one able to intervene on user profiles.
For property administrators managing a significant volume of co-properties, the issue of access traceability arises. Orchestrav2 does not publish an audit log accessible to end users. The supervision of connections and document consultations remains the responsibility of the EGI back-office, which can complicate responses to transparency requests made by the syndic councils.
Access to the Orchestrav2 portal relies on an architecture where the initial configuration conditions everything else. A property administrator who masters the creation of user profiles in the EGI business software, verifies email addresses, and understands the sensitivity to case of usernames eliminates the vast majority of connection issues encountered by their clients.