Sentrifugo is configurable, but some of that configuration lives in files, database columns, and server settings rather than friendly screens. That’s exactly the territory of a vibe-code agent, which can edit the app’s code and config while you watch and explain each change before it sticks. Here are ten customizations that make it feel like your HR system instead of a default install — some take minutes, one or two take an afternoon.
1. Rebrand Every Screen
The logo in the corner and the words on the login page are the first things employees notice. The agent can swap the logo and favicon for yours, rewrite the login-page copy, and adjust the CSS to your colors. Just as usefully, it tells you which files it touched, so you know what to re-apply after an upgrade instead of discovering the hard way. Try: “Replace the Sentrifugo logo and favicon with ours, put our support email on the login page, and shift the header color to our brand blue.”
2. Rework Employee Numbers With Identity Codes
Sentrifugo’s identity codes control how employee and user IDs are generated — prefix, padding, separators, and sequence. If finance wants IDs that match your ERP or sort cleanly in reports, this is where it happens. The agent sets the pattern, shows you how the next numbers will look, and confirms existing records stay untouched. Say: “Change new employee numbers to ‘OS-‘ plus the year plus a three-digit sequence, starting at OS-2026-001, and show me how the next five will look.”
3. Tune the Appraisal Model to Your Roles
The appraisal module runs on parameters grouped into competencies, with rating scales and weights — and generic parameters produce generic reviews. The agent can define parameters per department or role, so salespeople are rated on revenue and pipeline hygiene while engineers are rated on delivery quality, each with sensible weights. Try: “Create appraisal parameters for the Sales department with Revenue at 50%, Pipeline hygiene at 30%, and Teamwork at 20%, and make them the default for that department.”
4. Add a Custom Field to Employee Profiles
Sentrifugo profiles don’t track everything you need — cost center, desk number, emergency contacts in your format. Adding a field properly means a database column, a form input with validation, and a place in exports. The agent does all of it — column, form, validation, export — and keeps the permissions right so employees can’t edit what only HR should. It will also warn you if a future app upgrade expects the original schema. Say: “Add a ‘Cost Center’ field to employee profiles, editable only by HR, and include it in the employee data export.”
5. Build a Manager Dashboard That Shows Your Numbers
The default dashboard shows what it shows; your actual questions are different — approvals waiting on me, open requisitions, appraisal completion. The agent can add a page backed by real queries against the leave, recruitment, and appraisal tables, and lay it out so a manager gets the answer in one glance. Try: “Add a dashboard page for managers showing pending leave approvals, open requisitions, and appraisal completion percentages for their department.”
6. Rewrite the Email Templates in Your Voice
The stock emails are functional and bland, and their templates live in the code with merge fields that break if handled carelessly. The agent can rewrite the leave decision, interview invite, and welcome mails in your company’s tone, fix the placeholders, and test-send one to you before anything goes to a candidate. Say: “Rewrite the interview invitation email in a friendlier tone, include the video-call link automatically, and test-send it to me.”
7. Wire Up LDAP Login
If you run Active Directory or OpenLDAP, employees should sign into Sentrifugo with the same credentials they use everywhere else — one less password to reset and one less account to disable at offboarding. The agent configures the connection, maps LDAP groups to Sentrifugo roles, and verifies with a real test account. Try: “Connect logins to our Active Directory, map the HR group to the HR Manager role, and verify a test user gets in with the right permissions.”
8. Harden the Server Around the App
The PHP application is only as safe as what’s wrapped around it. The agent can force HTTPS redirects, add security headers, set up fail2ban rules that watch the login page for brute-force attempts, and trim the database account down to the privileges Sentrifugo actually uses. None of this shows in the UI, and all of it matters. Say: “Lock this server down: force HTTPS, block repeated failed logins, and make sure the Sentrifugo database user has no more rights than it needs.”
9. Housekeeping and Data Retention
Old resumes, rejected candidate records, and years of finished appraisals bloat the database and widen what any leak exposes. A retention job archives or prunes by age — rejected resumes after a year, appraisal archives moved out of the main tables — and writes a log of everything it removed, so deletion is a decision you can review rather than a hope about what happened. Try: “Delete resumes of candidates rejected over a year ago, archive appraisal data older than 2024 out of the main tables, and keep a log of everything removed.”
10. Fix Formats, Timezone, and Terminology
Small mismatches erode trust faster than big ones: dates in the wrong format, a timezone three hours off, or module names that don’t match your company’s language. The agent adjusts the site settings and language strings so the interface reads the way your people talk, and it checks the change on a real screen rather than assuming the setting took effect. Say: “Switch all dates to DD/MM/YYYY, set the timezone to Europe/Lisbon, and rename ‘requisitions’ to ‘job openings’ everywhere in the interface.”
Pick the one that irritates you most and have the agent do it while you read the diff. These are real edits to your server, and the agent should show you every one of them before and after. Run HR your way on a private server: Sentrifugo on OpenSysLab.
