On the ground, a City of Paris agent on the move who needs to consult a schedule or validate an HR document faces a simple constraint: accessing IntraParis without being at the office. The Nomades portal (nomades.apps.paris.fr) exists for this, but between authentication issues, Wi-Fi networks that block the connection, and sessions that expire, the reality of daily life is less fluid than the promise.
Nomadic connection to IntraParis: what’s blocking on the ground
The first reflex when trying to connect from the outside is to open a browser and type in the address of the Nomades portal. On paper, you enter your professional credentials, validate the SMS code for two-factor authentication, and access your email or HR services.
Related reading : How to Access a Vehicle's History for Free: Practical Guide and Tips
In practice, the SMS code doesn’t always arrive on time. If the phone number associated with the account is not up to date, the code goes into the void. And after several incorrect attempts, the account gets automatically locked. At this stage, the only solution is to call the IT support to unlock access.
A point often overlooked: the network used to connect makes all the difference. Some public Wi-Fi (hotels, train stations, coworking spaces) or corporate networks filter connections to institutional portals. If the page doesn’t load or shows a certificate error, it’s quicker to switch to your personal mobile network or a professional VPN rather than repeatedly trying on a blocking network.
Related reading : Tips and Practical Advice to Make Life Easier for Modern Moms
To properly configure the nomadic access to the IntraParis agent account, it’s best to check these network prerequisites even before entering your credentials.
Browser and cache: settings that avoid most bugs
The IT department of the City of Paris recommends using recent browsers, particularly Chrome or Edge. Firefox works in most cases, but some agents report display issues on internal service pages with older versions.
The reflex to adopt before any nomadic connection attempt:
- Clear the browser cache and cookies, especially if the last nomadic session was several days ago. Expired session cookies cause redirection loops on the authentication page.
- Check that the browser is up to date. An outdated version may not support the security certificates of the portal.
- Temporarily disable blocking extensions (like ad blockers or script blockers) that sometimes interfere with the login form or the loading of the 2FA code.
Feedback varies on this point, but several agents report that private browsing (incognito mode) resolves persistent session issues without having to manually clear the cache.
Mobile app Mon IntraParis: when the web portal is not enough
Alongside the Nomades portal accessible via browser, a mobile app “Mon IntraParis” is available on Android and iOS stores. It uses the same professional credentials as the web portal.
The main interest of the app can be summed up in one sentence: consult your internal email on the go without going through a browser. This avoids cache, cookie, and browser compatibility issues that represent the majority of support tickets related to nomadic connections.
What the app concretely allows
The app provides access to basic email and HR services. For agents who primarily need to read their professional emails or check administrative information between meetings, it’s often more reliable than a web connection on an uncertain network.
However, not all features of the IntraParis portal are always replicated in the mobile app. For advanced operations (document management, certain business forms), accessing the web portal remains necessary.
Agent account security: actions that protect professional data
Nomadic access opens an exposure surface that accessing from a fixed workstation on an internal network does not present. The Nomades portal even displays a legal warning reminding users of articles 226-15 and 323-1 to 323-7 of the penal code regarding unauthorized access attempts.
For an agent, the concrete precautions boil down to a few habits:
- Never save your IntraParis credentials in a shared browser or on a computer that is not yours. The password manager integrated into your personal browser is acceptable, but not one from a public workstation.
- Always log out at the end of a nomadic session. Closing the tab is not enough: use the logout button on the portal to invalidate the session token.
- Update your phone number in the account settings as soon as it changes. An outdated number blocks the receipt of the 2FA code and forces a call to support.
- In case of a forgotten password, the procedure goes through the dedicated reset page (vdp-gestionidentitenumerique.apps.paris.fr). There’s no need to call support for this operation.
First nomadic connection and password change
During the first connection to the Nomades portal, the system asks you to enter a new password. This password must meet the complexity criteria defined by the IT department. If the procedure fails or the change page does not display correctly, clearing the cache followed by reconnecting on a recent browser resolves the issue in the vast majority of cases.
Nomadic access to IntraParis works reliably as long as you master three variables: the network used, the state of the browser, and the update of contact information associated with the account. Most of the blocks encountered by agents do not stem from a portal outage, but from one of these three parameters misconfigured on the user side.