Medisys Portal and Medisysnet refer to distinct environments within the Medisys ecosystem, but confusion persists among many professionals. The difference is not just a matter of URL: it conditions access rights, usable data flows, and technical support procedures. Understanding this separation avoids recurring operational blockages, particularly regarding the reset of credentials and document visibility.
Remote Management and Service Status: What the Medisys Portal Exposes to Structure Managers
The Medisys portal includes a feature rarely discussed in user guides: the real-time service status page. Three indicators are distinguished, each monitoring its own technical scope.
- Mobile Remote Management: covers the reporting of interventions from field workers’ smartphones, with GPS timestamping.
- Fixed Remote Management: concerns badge readers and terminals installed in the premises of beneficiaries or structures.
- HR and Family Portal: reflects the availability of the web interface intended for employees, supervisors, and families.
For a structure manager, this tripartition allows for immediate isolation of the source of a malfunction reported by an operator. An incident in mobile remote management does not affect the consultation of schedules on the HR portal. We observe that this distinction is absent from most internal training, leading to misdirected support tickets.
You can learn more about Nouvelle Jeunesse to delve into the functional differences between these environments.
Medisysnet HR and Family Portal: Functional Scope and Access Rights
The address v2.medisysnet.fr corresponds to the HR and Family portal, currently in version V2.5.9. This portal targets two populations: employees (home helpers, life assistants, administrative staff) and the families of beneficiaries.
Documents and Schedules Visible According to Profile
A source of friction: the visibility of documents varies greatly from one account to another within the same structure. Payslips, intervention sheets, and individual schedules are not all accessible by default. The configuration depends on the rights assigned by the managing structure.
An employee who notices that their colleague has access to additional documents is not facing a bug. Rights are configured by the structure’s administrator, which implies rigorous management of authorizations during each hiring or position change.
Password Reset on Medisysnet
The process for recovering credentials differs depending on the portal used. On the HR and Family portal, the “forgot password” link is not available. The employee or family must contact the managing structure directly or go through the support portal to obtain a reset.
This constraint is not an oversight in design. It stems from a security choice: the credentials for the HR portal are linked to sensitive data (payroll, interventions, health data), and the reset procedure requires human verification on the structure’s side.
Medisys Client Space: The Support Portal Reserved for Managing Structures
The address espaceclient.medisys.fr opens a completely separate environment from the HR portal. This support portal is reserved for managing structures and their technical referents. It does not concern employees or families.
Functions of the Medisys Support Portal
The support portal centralizes remote maintenance, exchanges with the publisher, and incident tracking. It is from this space that administrators can manage password reset requests for their teams.
We recommend that structures designate at least two authorized referents on the support portal. In the absence of the sole referent, the structure loses its ability to unlock access for its employees, which paralyzes the consultation of schedules and the validation of interventions.
Frequent Confusion Between the Two Portals
The coexistence of v2.medisysnet.fr and espaceclient.medisys.fr causes daily connection errors. An employee attempting to log in to the support portal with their HR credentials receives a refusal without an explicit message. Authentication databases are compartmentalized: a single user may have two distinct sets of credentials with no link between them.
Mobile Access Medisys: Compatibility and Limits in 2026
The Medisys mobile application and mobile browser access to the HR portal do not cover the same scope. The mobile application focuses on field remote management: clocking in, intervention signatures, and real-time data transmission.
Access to the HR portal from a mobile browser works, but some features remain partially adapted to small screens. Consultation of schedules works correctly, while viewing payslips in PDF format depends on the browser’s built-in reader.
For structure managers, the distinction is operational: the mobile application feeds into remote management, while the web portal is used for consultation and administration. Mixing the two circuits creates duplicate clocking or loss of traceability on interventions.
Health Data Security on Medisys and Medisysnet
Medisys servers are hosted in France, meeting regulatory requirements for health data. The encryption of exchanges between the mobile terminal and the servers covers both fixed and mobile remote management.
The compartmentalization of the portals directly contributes to this security architecture. A compromised access on the HR portal provides no visibility on the support portal, and vice versa. This separation reduces the attack surface in case of credential leakage.
The management of access rights remains the responsibility of each structure. Medisys provides the configuration tools, but the assignment of authorizations is the responsibility of the local administrator. Regular audits of active accounts, especially after personnel departures, remain the best protection against unrevoked residual access.
