Authentication on MaBoxRH relies on a centralized circuit that serves both GTA (time and activity management) and GTM (shared time management). Access blocking does not always stem from an incorrect password. In a notable proportion of cases, it is the browser, a local security setting, or an accessibility issue with the virtual keyboard that prevents input even before authentication is attempted.
MaBoxRH Virtual Keyboard: Blockages Not Covered by Technical Support
The virtual keyboard on the MaBoxRH authentication page is the primary source of friction. It requires input via clicking or tabbing, making it sensitive to several local configurations that agents may not suspect.
A script blocker that is too strict (uBlock Origin in advanced mode, NoScript, or enhanced settings in Firefox) can prevent the virtual keyboard from rendering without displaying an error message. The page appears functional, but no digits appear in the password input area. The usual reflex is to clear the cache, while the problem lies with JavaScript filtering.
We recommend testing access in a private browsing window with extensions disabled. If the keyboard appears, the problem is confirmed on the extensions or browser security settings side.
To access GTA and GTM extranet La Poste without blockage, it is also necessary to ensure that the browser allows third-party cookies on the domain maboxrh.laposte.fr, as the centralized authentication circuit depends on it.
- Temporarily disable any filtering extensions (ad blockers, anti-trackers, privacy shields) before loading the login page.
- Check that JavaScript is enabled in the browser settings, not just at the extension level.
- On Chrome, ensure that the setting “Prevent sites from using third-party cookies” is not checked for this domain.
- On a work computer, check with the network administrator if a proxy or corporate firewall is filtering requests to maboxrh.laposte.fr.
Accessibility of the GTA Virtual Keyboard with a Screen Reader
MaBoxRH offers an audio version of the virtual keyboard, which can be activated via a “Activate Sound” button located just before the grid of numbers. This feature is documented on the site’s accessibility help page, but its actual functioning poses constraints that visually impaired or blind agents often discover on their own.
With JAWS or NVDA, navigation within the virtual keyboard is done exclusively by tabbing, not by arrow keys. This is a crucial technical point. A user accustomed to navigating with arrows in other web forms will not be able to traverse the digits. The Shift + Tab combination allows going back, and each digit is confirmed by the Enter key.
Another peculiarity of MaBoxRH: navigation between sections of the site does not trigger a new page load. The content updates in the current page. After clicking on an internal link, the screen reader cursor remains on the activated link instead of being repositioned at the top. The official documentation recommends navigating by main landmark or heading level to reach the updated content.
This single-page architecture (SPA) is common on modern HR portals, but it significantly degrades the experience with a screen reader if the user is not aware of this peculiarity.
Password Reset GTA GTM: Centralized Circuit and Blocking Cases
The reset procedure goes through a dedicated form on MaBoxRH. The agent enters their HR identifier, and a reset email is sent. This circuit is common to both GTA and GTM, meaning that a single password provides access to both modules.
Blocking occurs in two cases that the form does not cover:
- The agent has forgotten their secret answer and their work email is inaccessible. A specific link “I forgot my secret answer or my email is inaccessible” exists on the reset page, but it redirects to a manual procedure that requires contacting support.
- The email address associated with the account is outdated (change of site, transfer, change of status). In this case, only the local HR or the hierarchical manager can resolve the situation.
The technical support accessible at [email protected] handles technical connection incidents. Requests related to personal information, rights, or schedules fall under local HR. Confusing the two circuits prolongs the resolution time.
Browser and TLS Version: Often Ignored Network Prerequisites
MaBoxRH uses HTTPS with TLS version requirements that eliminate outdated browsers. An agent attempting to connect from an old machine using Internet Explorer or an outdated version of Safari may encounter a blank page or a certificate error without an explicit message.
Compatible browsers are those that support at least TLS 1.2. In practice, this excludes Internet Explorer 10 and Android versions prior to version 5. On tablets, the default built-in browser is sometimes too old even if the system appears up to date.
On a public Wi-Fi network or a mobile hotspot, some captive portals intercept the HTTPS request and cause a silent failure. The quickest test is to switch to a direct mobile network (cellular data without sharing) to isolate the problem.
The accessibility statement of MaBoxRH was updated in 2024, confirming that the portal is subject to active regulatory monitoring. This point is rarely mentioned, but it means that agents can report an accessibility defect as a regulatory incident, not just as a comfort issue. The channel remains technical support for functional aspects, and local HR for anything related to rights, schedules, and personal data.