GTm Extranet and MaBoxRH consistently appear in the searches of La Poste Group agents facing connection issues. However, these two names refer to distinct technical realities, and the confusion between them is the primary cause of authentication failure, even before password errors. This article lays out the facts regarding their relationship, the concrete pitfalls related to accounts, and the known limitations of the current ecosystem.
Three La Poste accounts that do not share the same login procedure
A point rarely explained in internal guides deserves to be stated upfront: three accounts coexist without any technical link between them. The GTA/MaBoxRH account, linked to the HR identifier (IDRH), is exclusively used for professional processes (scheduling, leave, absences). The public La Poste account, used for mail-parcel services and Digital Identity, relies on a separate infrastructure. The laposte.net messaging system constitutes a third silo.
The direct consequence is that a reset performed on laposte.fr does not resolve a blockage on MaBoxRH. An agent who confuses these areas may multiply attempts on the wrong portal, worsening the situation instead of resolving it.
To clearly understand the differences between GTM Extranet La Poste and MaBoxRH, one must first grasp this strict separation of accounts, which conditions the entire troubleshooting logic.
GTm Extranet La Poste: an integrated module, not a standalone site
GTm Extranet is not an independent portal with its own URL. It is the time and activity management module embedded in the portal maboxrh.laposte.fr. In practice, no one connects “to GTm” directly: authentication goes through MaBoxRH, which manages identification via IDRH and the virtual keyboard, then redirects to the GTm module once the session is opened.
This architecture has a concrete implication for diagnosing failures. If the MaBoxRH login screen appears but GTm does not load afterward, the problem likely lies with the application module or the session, not the authentication. Conversely, if the login screen itself is inaccessible, the entire MaBoxRH portal is at fault (maintenance, incompatible browser, network filtering).
MaBoxRH also consolidates other HR functionalities beyond GTm: viewing pay slips, tracking training, accessing contractual information. GTm only covers the time and activity aspect (leave balances, RTT, CET, schedules).
MaBoxRH account lockout: what happens after several failures
The automatic lockout mechanism is an operational point that most agents discover in an emergency. After several failed login attempts, MaBoxRH temporarily blocks access. Persisting with new attempts only prolongs the lockout.
The recommended procedure follows a precise order:
- Wait several minutes before any new attempt, to allow the temporary lock to expire
- Use the password reset function if the lock persists after this delay
- Contact the local HR support or the dedicated address ([email protected]) if the reset does not work
The virtual keyboard on the authentication page adds a layer of difficulty. The numbers of the password must be entered by clicking on this keyboard, not by typing on the physical keyboard. A common mistake is to press the keys on the standard keyboard reflexively, resulting in input failures without an explicit error message.
Mobile connection to MaBoxRH and GTm: documented limitations
Access from a smartphone or tablet works, but reliability is lower than on a desktop computer. Several constraints accumulate on mobile.
The virtual keyboard, designed for a wide screen, becomes difficult to manipulate on a small screen. The detailed consultation of leave counters or GTm schedules loses readability. Disconnections may occur during redirects between the MaBoxRH portal and the GTm module, requiring re-authentication.
For agents on the move who need to regularly check their schedules, favoring an up-to-date browser on a computer remains the most stable solution. On mobile, limiting usage to occasional consultations reduces the risk of session loss.
Convergence of La Poste portals: where do we really stand
Since the convergence initiated between MaBoxRH, GTm Extranet, and the Smart Portal, the boundary between the interfaces has blurred. Field feedback varies on the actual degree of synchronization between these tools. The convergence has not yet produced a fully unified solution officially confirmed.
This ambiguity has concrete effects for users:
- Some functionalities appear in MaBoxRH but redirect to a separate sub-portal, sometimes requiring a new authentication request
- Updates to personal data made on one portal do not always immediately reflect on the others
- Agents transferred or in internal mobility may see their GTm account deactivated while their MaBoxRH access remains functional, necessitating specific reactivation with the HR service
The available data does not allow us to predict when this convergence will lead to a truly unified portal. In the meantime, treating each module as a distinct tool with its own constraints remains the most reliable approach to avoid blockages.
The key takeaway for optimizing daily connection lies less in a choice between GTm Extranet and MaBoxRH than in understanding their interconnection. An agent who correctly identifies which account to use, which portal to query, and which support to contact resolves the vast majority of access issues without going through a lengthy reset procedure.
