
The agents of the Orléans-Tours academy have several digital entry points to manage their professional lives. Two of them frequently come up in discussions: the PIA (academic intranet portal) and Arena. Despite a common authentication, these two platforms do not provide the same services and do not grant access to the same resources. The confusion is even more common as a third player, Colibris, has recently taken over some HR processes that were previously scattered.
Single authentication and distinct scopes: what the common gateway hides
PIA and Arena share the same username/password pair, that of the academic email. This is the main source of confusion: an agent who logs into the PIA can switch to Arena without re-authenticating, which gives the impression of a single portal.
You may also like : How to Optimize the Loading and Capacity of a 15m3 Truck for Your Moves
In reality, the scopes are separate. The PIA is a local academic intranet, managed by the Orléans-Tours rectorate. It hosts the academy’s news, internal documentation, links to assistance (Passion for the first degree, dedicated email for the second degree), and institutional information specific to the academy.
Arena, on the other hand, is a national portal deployed across all academies. It provides access to business applications managed by the ministry: student management, grading tools, services related to exams and competitions, I-Prof. The agent looking to consult their career file or enter grades goes through Arena, not through the PIA.
You may also like : Discover how Nantes' tram line 2 facilitates access to the city center
A resource detailing access to the PIA and the Arena portal Orléans-Tours allows for a visualization of these concrete differences in scope.

Arena Portal Orléans-Tours: national applications and recent migration
Arena underwent a technical overhaul at the end of 2024. Since November 7, 2024, according to an information relay from the rectorate’s DSI, access to the new Arena portal has posed difficulties for many agents. The recommended procedure is to go through the academic site (ac-orleans-tours.fr), then through the quick access “Espace pro Pia” to reach the updated authentication page.
This new authentication page distinguishes two scenarios:
- Agents without an OTP key enter their username and password directly on the home screen.
- Agents with an OTP key (enhanced security device) use a PIN code associated with this key, in addition to their username.
- In case of account blockage (detection of a security issue), the agent is redirected to the “Blocked Access” application hosted on the academic domain, before being able to access Arena or the PIA.
The OTP key adds a layer of authentication that does not change the scope of accessible applications, but conditions actual access to the portal. An agent whose account is blocked cannot access Arena, the PIA, or webmail, as all three are linked to the same identity reference.
PIA Orléans-Tours Academy: a local intranet often underestimated
The PIA is not limited to a homepage with links. It serves as an academic dashboard. The section “My applications, my tools” groups shortcuts to services that may themselves be hosted on Arena or other platforms. This is what maintains the confusion: by clicking on a link from the PIA, the agent sometimes finds themselves on Arena without realizing it.
The PIA also hosts the charter of use for the information system that each agent is required to respect. This document reminds that the username and password are strictly personal, and that the DSI will never ask for this information by email, a point regularly emphasized in light of phishing attempts.
What the PIA no longer does
Several HR processes that previously went through the PIA or Arena have migrated to Colibris. The ministry now positions Colibris as the single entry point for mobility and career: submission of wishes, derogatory requests, tracking of transfer steps. For management staff, a binding calendar has been published for 2025.
This redistribution creates a three-level mapping that agents must integrate:
- PIA for the local academic intranet (news, documentation, assistance).
- Arena for national business applications (I-Prof, student management, competitions).
- Colibris for structuring HR processes (mobility, career, administrative requests).
Field feedback varies on the clarity of this distribution. Some agents report that links to Colibris are accessible from the PIA, which further blurs the boundary between the portals.

Blocked account and troubleshooting: the real journey of an agent in difficulty
The most common scenario remains account blockage. The academy has set up a dedicated application, accessible at bv.ac-orleans-tours.fr/acces-bloque. This blockage generally occurs after an automatic detection of a security anomaly, not necessarily after a password error.
A blocked account simultaneously cuts access to the PIA, Arena, and webmail. The agent must resolve the blockage before being able to access either portal. For the first degree, assistance goes through the Passion tool (accessible via the extranet). For the second degree, the channel remains the email at [email protected].
The distinction between PIA and Arena has no impact on the unblocking procedure: the identity reference is common. However, once the account is restored, the agent must know which portal to go to depending on their need, lest they search for an HR application on Arena when it has migrated to Colibris.
The proliferation of portals with a single identifier gives a false impression of simplicity. Three platforms, three functional scopes, one password: it is the mapping of uses that is lacking, not the authentication. As long as the academy does not display an explicit routing upon login, agents will continue to confuse the entry point with the room they need to go to.