Pyla brings together in one place everything a company entrusts to its employees and contractors (laptops, phones, software, licenses, badges, vehicles, PPE) and keeps it up to date at every arrival, internal move and departure.
Connected to the HRIS, Pyla coordinates the employee lifecycle across HR, managers, IT and the other teams involved. When someone joins, changes role or leaves, each person in charge of a resource is informed in advance, with the information they need, and Pyla follows up until the job is done. At any time, IT knows who holds what. In short, Pyla is an IT onboarding and offboarding platform covering the full joiner-mover-leaver (JML) process.
Pyla is built and hosted in France. It is used by IT teams at companies with 200 to 5,000 employees, where a small IT department has to keep up with a constant flow of arrivals and departures.
THE PROBLEM
Each arrival, internal move or departure (permanent staff, fixed-term contracts, interns, apprentices, temps, contractors) involves 5 to 10 people who have to prepare or take back resources: laptop, phone, email, ERP and CRM access with role-based rights, business software, badges, safety equipment, company car. A company catalog usually holds around a hundred of these items, each with its own owner.
No one coordinates the whole process, and IT bears the consequences. HR informs IT late, and often not at all when someone leaves. Managers forget the form or fill it in at the last minute. IT, facilities and finance receive incomplete information and keep chasing answers. PC or Mac? Which rights in the ERP?
Departures are the weakest point. IT is often not informed and has to search tickets and emails to find out what was assigned. Disabling SSO is not enough: licenses have to be released, equipment recovered, mailboxes handed over, and any access outside the identity provider removed. Internal moves are rarely handled at all, so new rights pile up on top of old ones.
For the CIO, this means an overloaded IT team, access left open and hard to prove closed during ISO 27001, NIS 2 or statutory audits, licenses paid for people who have left, and equipment that never comes back.
HOW PYLA WORKS
When someone joins, changes role or leaves, the HRIS notifies Pyla. Pyla asks the manager what the person needs, or applies the package already defined for their profile. Each resource owner (IT, facilities, finance, HSE, business application owners) then receives an assignment or removal request ahead of time, with automatic reminders. When the person leaves, Pyla lists everything that was assigned to them so it can be removed or returned. The full history is kept for audits.
1. Resource catalog and owners
The company lists everything it assigns to people, IT and non-IT, and names the person responsible for assigning and removing each item.
2. Profiles and assignment rules
Rules define which resources each employee profile is entitled to, based on job, department, site, contract type or any other HR attribute. Advens defined 30 employee profiles, each with its own package of equipment, software and badges. HR only enters the person and their profile, and all requests are sent.
3. Managers involved only when needed
Managers receive a pre-filled package to confirm or adjust, rather than a blank form. When a profile is fully configured, the manager does not need to do anything.
4. Approvals
Access to sensitive applications can require approval. At Akiem, an arrival triggers a request for access to the treasury software Kyriba. The CFO approves it, then IT support grants it.
5. One consolidated ticket in the IT service desk
Pyla creates a single, complete ticket in GLPI or Jira instead of dozens of separate ones. When the ticket is closed, the related tasks in Pyla close as well. Teams that do not use IT ticketing, such as facilities or finance, handle their tasks directly in Pyla.
6. Lifecycle tracking
Assignments, returns, inventory and stock are tracked in one place. The inventory module links laptops and phones to employee movements, so the asset register stays current.
KEY CAPABILITIES
- Arrivals, internal moves and departures detected from the HRIS
- Predefined packages by employee profile (role-based access control)
- Tasks sent to each resource owner, with deadlines and automatic reminders
- Needs confirmed by the manager through a short, pre-filled form
- Approval steps for sensitive applications
- Consolidated ticket in GLPI or Jira, with closure synchronized
- Departure checklist of everything assigned: access to remove, licenses to release, equipment to recover
- Dashboard of missed or incomplete offboardings, to remove orphan accounts
- Contractors, temps and intermittent workers handled in the same workflows, including returns
- IT and non-IT asset tracking, with inventory and stock management
- Activity history: who requested, who approved, who did what and when
- Export of an employee's full history in one click for ISO 27001, NIS 2 and statutory audits
- Open API to automate account creation and deletion, or to connect other systems
WHAT PYLA IS NOT
Pyla works alongside the tools a company already uses.
- Pyla is not an HRIS. It connects to it. Lucca and BambooHR have native connectors, and ADP, Cegid TalentSoft, Nibelis, PeopleSphere, CrossTalent and Sedit are already connected at customer sites.
- Pyla is not an IT ticketing tool. It connects to GLPI or Jira and sends them a consolidated ticket.
- Pyla is not an IAM. It does not create accounts the way Okta or Microsoft Entra ID do. It organizes who does what and when, and covers what an IAM does not see: hardware, badges, phones, PPE and applications outside the directory. iBanFirst uses Pyla together with Okta.
- Pyla is not an HR onboarding experience tool. There are no welcome booklets or quizzes. It is an operational tool built for IT.
Pyla typically replaces spreadsheets, email lists, SharePoint, Microsoft Forms, Power Automate flows and in-house apps that nobody maintains once their creator leaves.
INTEGRATIONS
- HRIS: Lucca and BambooHR (native connectors), ADP, Cegid TalentSoft, Nibelis, PeopleSphere, CrossTalent, Sedit
- IT service management: GLPI, Jira
- Directory: Active Directory account creation and deletion through the API
- Email: mailbox creation through the API
- Open REST API
WHO IT IS FOR
Pyla suits companies with frequent movements (hiring, contractors, temps, seasonal or intermittent workers), many different job profiles, several sites, critical business software, an HRIS that is not connected to IT, and a small IT team using GLPI or Jira. It is particularly useful for companies working toward ISO 27001 certification and for organizations covered by NIS 2.
Main users: CIOs, IT support and infrastructure managers, IT project managers and CISOs, along with managers, HR, facilities and finance.
CUSTOMER RESULTS
- Studio TF1 (TV and film production): about 1,000 movements a year for a workforce of around 1,000, half of them intermittent workers who come and go. Production assistants enter requests themselves, and access is closed at the end of each contract, including expensive licenses such as Adobe Premiere.
- Cap Ingelec (engineering for data centers and laboratories, several sites): handles more than 360 movements a year with a 12-person IT department, without extra workload. GLPI handles incidents, Pyla handles the employee lifecycle and shows missed offboardings.
- iBanFirst (fintech, 350 employees): half of the workforce is in sales, with high turnover. The HRIS triggers each arrival and departure in Pyla, and a new salesperson automatically generates tasks for the Salesforce, HubSpot and Modjo owners. Okta handles account creation in parallel.
- CFDT: replaced an in-house SharePoint and Word tool after access stayed open for months after some departures. Pyla is connected to the HRIS, Active Directory and GLPI, and internal control provides access review evidence to statutory auditors.
- Advens (cybersecurity): moved from tickets split by hand to 30 employee profiles, automated Active Directory accounts and full traceability for ISO 27001.
- Akiem (locomotive leasing, 20+ countries): replaced an outdated in-house tool and chose Pyla over Jira. IT, facilities, PPE and credit cards are managed in one tool, with one view per employee instead of scattered tickets.
- La Maison Bleue (nursery network): Pyla is the single link between the HRIS and the IT service provider, and mailboxes for field staff are created automatically.
- Groupe Revue Fiduciaire: after finding that a former employee still had editorial access six months after leaving, the company centralized all arrivals and departures in Pyla.
Also used by Shippeo, Takara Bio, Kercia, FIC Expertise and CTN France.
WHY TEAMS CHOOSE PYLA
- Simpler than IAM or ITSM suites, which are complex and costly for mid-sized companies, and better suited to coordinating several teams than an IT ticketing tool
- One view per employee, with everything they hold
- Non-IT resources included, not only accounts and laptops
- Evidence ready for ISO 27001 audits (Annex A controls on HR security, asset management, return of assets and access rights) and for NIS 2
- French company founded in 2020, data hosted in France (OVH), support in French and English
- Listed with UGAP for French public sector buyers
- Up and running in a few days to a few weeks, with your team trained to manage the platform on its own
- Per-employee pricing with unlimited users and assets, decreasing with company size and contract length
LEARN MORE
- IT onboarding: getpyla.com/onboarding-it
- IT offboarding: getpyla.com/offboarding-it
- Access governance: getpyla.com/gestion-habilitations-informatiques
- IT and non-IT asset management: getpyla.com/gestion-actifs-informatiques
- Customer stories: getpyla.com/clients
- Book a demo: getpyla.com/demande-de-demo
Who Is the Company Behind Pyla?
-
Seller: Pyla
-
Year Founded: 2021
-
HQ Location: Paris, FR
-
LinkedIn® Page: www.linkedin.com
7 employees on LinkedIn®
