France Sécurité Prévention
Website, intranet and documents for a CNAPS-licensed private security company
France Sécurité Prévention (FSP) is a CNAPS-licensed private security company based in Normandy, France. I am part of its IT team. I developed its website and intranet, listed the documents a company in this sector must be able to produce, ran acceptance testing before going live, and I now look after maintenance, new features and SEO.
- Sheet
- 04 · France Sécurité Prévention
- Period
- Apr. 2026 → today
- Status
- In productionPrivate production
- Role
- IT team · website, intranet, documents, testing, maintenance, SEO
- Online
- fsp-securite.frintranet.fsp-securite.fr · private system
- Technology
- React · Vite · PocketBase · Hooks serveur · PDF · QR vCard · Nginx · Ubuntu 24.04 · VPS LWS · Zoho SMTP
- Revision
- Website in production · intranet in private production
The project in motion
Transcript
15-second film, no voice or music. Title “France Sécurité Prévention”, then a frame draws itself and real screenshots of the project follow inside it; below, the layers I worked on light up. It ends on the project's address.
A website that reassures before the first call
A client looking for a security company first wants to know whether it is licensed and knows its job. So the website presents FSP's services, from SSIAP fire safety to dog handlers, the sectors it works in, from logistics to construction sites, and a page dedicated to its certifications: CNAPS licence, SSIAP qualifications, collective agreement, GDPR compliance.
- A contact form that adapts: quote request, spontaneous application or partnership proposal, each with its own fields.
- An FAQ sorted by category: quotes, recruitment, regulations, to answer before anyone has to pick up the phone.
- A cookie banner that follows CNIL rules: refusing is as easy as accepting.
- A full admin area: the company publishes its own job offers, news, FAQ, images and an announcement banner, and receives applications and messages.


63 documents before a single line of code
Before building the intranet's document generator, I listed everything a French private security company must be able to produce or hold, from the pre-hiring declaration to the staff register. For each of the 63 documents, the catalogue states what it is for, when to use it, who it is for, whether it is required by law, by the CNAPS or by the collective agreement, and whether FSP already had it.
| Family | Examples |
|---|---|
| Human resources | Permanent and fixed-term contracts, amendments, leave, employment certificate, final settlement, employer registers |
| Private security | Regulatory documents required by the CNAPS, operational documents in the field |
| Clients and finance | Service contracts, invoices, social compliance certificate |
| Legal | Company documents, GDPR policy, internal memos |
One portal per job
The intranet gives everyone the screen they need: management steers, HR manages staff, operations organises the sites, the site supervisor reports from the field, the guard checks their schedule and the client follows their services. During acceptance testing in July 2026, I checked all 113 menu entries for each of the seven roles.
- — Accounts
- — Audit log
- — Email templates
- — Settings
- — Dashboards
- — Payroll
- — E-signature
- — Directory
- — Recruitment
- — Onboarding
- — Employees
- — Contracts
- — Leave
- — Compliance
- — GED
- — Sites
- — Assignments
- — Scheduling
- — Timesheets
- — Incidents
- — Client requests
- — Team
- — Incidents
- — Field reports
- — Schedule
- — My site
- — Timesheets
- — Documents
- — Leave
- — Pro card
- — My sites
- — Requests
- — Incidents
- — Reports
- — Documents
- HR: recruitment, onboarding, employee records, document vault, contracts, leave.
- Operations: sites, assignments, scheduling, timesheets entered by day or by week, incidents.
- Field: guards see their schedule, site and documents; site supervisors file incidents and reports with photos.
- Clients: each client follows their own sites, requests and reports, and only theirs.

◆ NoteI do not show the internal screens: they contain real employee and client data.
Signing without printing
I added an e-signature module. Each signer gets a link, reads the document, signs by hand or by typing and gives consent. The document is then sealed with a SHA-256 fingerprint, and a certificate records every step: opened, signed, sealed.
One colour per role
The intranet also generates the team's business cards. The front stays white, the back navy, and only one accent colour changes with the role, on the edge line and the job title. On the back, a QR code saves the contact to the phone in one scan. The cards come out in the standard 85 × 55 mm format, one at a time or on an A4 sheet of ten.
- Management
- Gold · #C9A84C
- HR
- Purple · #7C3AED
- Operations
- Blue · #002395
- Site supervisor
- Cyan · #0891B2
- Guard
- Red · #ED2939
- Client
- Grey · #64748B
173 tests before going live
I wrote a test plan of 173 numbered tests in twenty parts, from the public website to the client portal. Each test is ticked OK or KO, and an issue is reported simply by its number. After my run, I gave the company a summary of the issues sorted by theme, with the planned fix and its priority, before touching the code.
| Finding | Fix |
|---|---|
| Hiring emails were sent from a “noreply” address: candidates' replies were lost. | HR emails are sent from the HR address, which receives the replies. |
| Accents in acknowledgement emails were broken. | Email templates encoded in UTF-8. |
| Clients were not told when their request moved to “in progress” and then “closed”. | An email to the client at each status change. |
| A contract was generated automatically when a guard account was created. | A contract is now only created by HR. |
| Timesheets lost their values once approved. | Values kept and history visible, entry by day or by week. |
The same test run doubled as a permissions audit. I tightened them: a client only sees their own requests, and contracts can only be read by management, HR and the employee concerned. I also moved email sending to the server.
Visibility and maintenance
I manage the website's SEO with Google Search Console and Bing Webmaster Tools. I remain in charge of the website and intranet: updates, fixes, new features, backups and troubleshooting, on an Ubuntu server I administer, behind Nginx.

How I built it
- Requirements with FSP's management
- Document catalogue
- Test plan and issue summary
- Deployment, maintenance, SEO
- Website and intranet code
- Fixes after testing
What I take away
- A required field that is never sent makes a record fail without any message. Since then, I check what is actually saved, not just what is displayed.
Online
These addresses were responding on Oct 7, 2026.
- fsp-securite.frIn production
- intranet.fsp-securite.frPrivate production
