The login procedure for MyArkevia relies on a precise technical sequence that most consumer guides oversimplify. HR registration number, personal email address, temporary activation code: each element plays a distinct role in the authentication chain. Understanding this mechanism prevents recurring blocks and loss of access after a job change.
Arkevia Authentication Chain: What Happens on the Server Side
The Arkevia architecture strictly separates the employer’s repository from the employee’s account. The HR service generates an activation code linked to the employee’s payroll registration number, but this code does not pass through the company’s internal systems. It is transmitted by Cegedim SRH via a separate channel, usually a dedicated letter or email.
This separation means that the employer never has access to the employee’s personal identifiers. The password created during the first login remains unknown to the payroll service. In case of loss, only the employee can initiate the reset via the email address associated with the account.
We recommend checking a often-overlooked point: the email address provided during activation must be a personal address, not a work address. If you leave the company, the @employer.fr address will be deactivated, and the password recovery procedure will become impossible without Cegedim support intervention.
The login to my Arkevia space then follows a standard username/password flow on the myarkevia.com portal, without going through a corporate SSO.
MyArkevia Account Activation: Technical Errors That Block
The activation code provided by HR has a limited validity period. After this period, the link or code expires, and a reissue must be requested from the payroll service. This is the primary cause of blockage reported by employees.
Three situations systematically cause activation failure:
- The registration number entered does not exactly match that of the payroll system (pay attention to leading zeros or establishment prefixes that some HRIS automatically add).
- The email address provided contains a typo, preventing the receipt of the validation link and making the account inaccessible from the start.
- The browser blocks third-party cookies or uses a private browsing mode that prevents the persistence of the activation session on the Cegedim portal.
An activation failure does not erase the account. The vault already exists on the server as soon as the employer has provisioned it. Only employee access remains locked until activation is finalized. The documents deposited by the employer in the meantime are retained and will appear upon the first successful login.
Arkevia Login After Leaving the Company
Access to the vault does not depend on the employment contract. The account remains active even after the contract is terminated, and electronic pay slips remain available for 50 years or until the retirement age plus six years, according to the most favorable formula.
However, the former employer stops depositing documents there. The new employer, if also using Arkevia, will provision a separate space or feed the same vault according to the configuration chosen by their own payroll service. We observe that this cohabitation of flows from several successive employers is poorly documented by Cegedim.
A point of caution often ignored: the employer remains responsible for the integrity and availability of the pay slips, even when hosting is delegated to an external provider. If Cegedim changes its service conditions or ceases operations, it is the initial employer who must ensure access continuity. In practice, we recommend regularly downloading your documents and keeping a local copy or on a second medium.
Right to Object to Electronic Pay Slips
The employee can refuse the dematerialization of their pay slips, even after initially accepting the system. The employer must inform the employee of this right before the first dematerialized pay slip. Once the objection is made, the company has a maximum of three months to revert to paper format.
This right of objection does not delete the existing Arkevia account or the documents already deposited. It only interrupts the flow of new electronic pay slips.
MyArkevia Portal Security: Parameters to Check
Arkevia uses AES-256 encryption for stored documents and an HTTPS connection for exchanges. The portal does not natively impose two-factor authentication (2FA), which is a weakness compared to current standards for digital vaults.
To compensate for this absence, we recommend three measures:
- Use a unique password of at least twelve characters, distinct from any other online service, and store it in a password manager.
- Regularly check the recovery email address associated with the account. If it becomes outdated, change it immediately from the profile settings.
- Download pay slips in PDF format as soon as they are deposited. Each pay slip should remind the employee to keep it indefinitely, and a local copy protects against any technical mishap from the provider.
The personal space is limited to 100 MB by default, and each file uploaded by the employee cannot exceed 2 MB. These storage constraints require regular sorting if you use the space to archive personal documents in addition to the pay slips deposited by the employer.
The Arkevia vault fulfills its role of long-term storage as long as it is not the sole storage point. An independent copy of your pay slips, on an encrypted disk or a second digital vault, remains the best guarantee against contractual changes between your employer and Cegedim SRH.
