Leantime covers the basics well out of the box, but every team has its own process, brand, and ops standards. Your vibe-code agent can reach the configuration, the theme files, and the database on your server, so these ten customizations are plain-language requests rather than weekend projects. Some take five minutes, one of them is genuinely a half-day — we’ll flag which is which.

1. Make Email Actually Deliver

Leantime’s reminders and digests only work if the mail settings and the scheduler are right — the classic broken piece of a self-hosted install. Have the agent verify the SMTP configuration, send a real test message, and confirm the cron job that fires scheduled emails actually runs and logs. Almost every “my team isn’t getting notifications” story ends here. “Check my mail settings, send me a test email, and make sure the cron job that fires scheduled notifications is in place and logging.”

2. Rebrand the Login Screen and Colors

Your team looks at Leantime every day; make it yours. The agent edits the theme to show your logo, your company name, and a primary color from your brand guide. It backs up the original files first, so a bad edit is one command to undo — no reinstall anxiety. “Replace the Leantime logo with our company logo, set the accent color to #2F6FED, and change the page title to OurCompany Projects.”

3. Rename Columns and Tags to Match Your Process

The default kanban columns (Backlog, To Do, Doing, Done) rarely match how a real team works. Ask the agent to rename the board flow to your actual stages and rebuild the tag list into a clean taxonomy, merging the near-duplicates that accumulate over months. Filtering and reporting get useful again. “Rename the board columns to Intake / Scoped / In Build / In Review / Shipped, and merge my duplicate tags into one set organized by function.”

4. Build Project Templates You’ll Reuse

If every client engagement looks the same, stop rebuilding it from scratch. The agent creates a template project with your standard milestones — say Kickoff, Data Import, Training, Go-Live — plus the starter to-dos under each, and documents the one-step copy for each new client. “Create a Client Onboarding template project with milestones Kickoff, Data Import, Training, and Go-Live, ten starter to-dos spread across them, so I can clone it per new client.”

5. Add a Custom Field via a Small Plugin

Sometimes you need data Leantime doesn’t track natively — a risk rating, a contract value, a delivery method. Leantime’s official custom fields plugin covers this for some setups, but your agent can also scaffold a minimal plugin of its own that adds the field to every to-do. Honest note: this is the half-day item on the list, so expect an iteration or two, and test it on one project before trusting it with real data. “Write a small plugin that adds a Risk dropdown — low, medium, high — to every to-do, and show me how to keep it working across Leantime updates.”

6. Plug in SSO With OIDC or LDAP

If your team already lives in Google Workspace or Microsoft 365, a separate Leantime password is friction and a security gap. The agent configures OIDC or LDAP against your identity provider, maps groups to Leantime roles, and tests one real login before anyone else touches it. Keep the password login enabled as a fallback until the whole team has signed in once through SSO. “Set up OIDC login against our Google Workspace, map our existing groups to Leantime roles, and test it with my account first.”

7. Tune the Defaults for Your Team

Timezone, date format, and language sound trivial until half your team is reading due dates a day off. Have the agent audit the company settings and set sane defaults for where you actually operate, so sprint dates, milestone deadlines, and the calendar all agree. “Set the company timezone to Asia/Bangkok, the date format to DD/MM/YYYY, and the default language to English, then confirm the change took effect.”

8. Set Up Backups With a Real Restore Test

A backup you’ve never restored is a hope, not a backup. The agent sets a nightly job that dumps the Leantime database and archives the uploaded files into dated snapshots, keeps 30 days, and schedules a monthly restore into a scratch database to prove the dumps are good. If you can, ask it to copy the backups off the server too — a backup on the same disk as the data isn’t much of a backup. “Set up nightly backups of the Leantime database and user uploads to /backups, keep 30 days, and schedule a monthly test restore into a scratch database that emails me the result.”

9. Harden the Install

Self-hosted means you own the patching and the perimeter. Ask the agent to audit the instance: current version versus the latest release, file permissions on the upload directory, any leftover default accounts, which API keys exist and who owns them, and whether public self-registration is off. “Audit this Leantime install: check the version against the latest release, tighten file permissions, list every API key and who owns it, and confirm strangers can’t self-register.”

10. Prune the Database for Speed

After a year of daily use, old notifications, expired sessions, and long-dead rows bloat the database and slow the UI. The agent identifies the largest tables, purges what’s safe — with a backup taken first, obviously — and reports the before-and-after sizes so you can see exactly what changed. Run it every few months and the cleanup takes minutes instead of an afternoon. “Find the ten largest tables in the Leantime database, purge notifications and sessions older than six months, and show me the sizes before and after. Take a backup first.”

None of these need a developer on retainer — they’re an afternoon of chatting with your agent while it reads, edits, and tests. Start with email delivery, because every notification-dependent improvement builds on it. Leantime on OpenSysLab