OpenProject ships with sensible defaults and a long settings tail: work package types, workflows, custom fields, roles, notifications, and the plumbing underneath — SMTP, HTTPS, backups, monitoring. The Vibe-code agent can walk that tail with you, changing one thing at a time and explaining the trade-offs before it touches your data. These ten customizations are the ones owners ask for most.

1. A work package type that fits your process

The built-in types cover generic work, but most teams have at least one process that needs its own lifecycle with its own approval gate. The agent adds a type — say Change Request — with its own statuses and a role-based workflow, so only a project admin can move an item to Approved. Workflows are configured per type and per role, which is exactly the granularity that makes the admin screens painful to click through by hand but easy to state in one sentence. Say: “Add a Change Request work package type with statuses New, In Review, Approved, and Implemented, where only the PM role can move a request to Approved.”

2. Custom fields that carry your vocabulary

Custom fields put your categories on work packages: a Client impact list, a Risk level, a Sign-off date. The agent creates them, makes them mandatory where it matters, and adds them to the card and table views so people actually see them instead of ignoring a field hidden on page two. Say: “Add a mandatory Client impact list field with Low, Medium, and High to all task types, and show it on the cards in boards.”

3. Project templates you can stamp out

If every client engagement looks alike, templating pays for itself the second time you use it. The agent turns your best project into a template — wiki skeleton, meeting series, standard work packages, saved filters — and gives you a one-line way to clone it with the names swapped, instead of copy-pasting work packages by hand. Say: “Turn the Website Build project into a template I can stamp out for each new client, with their name in the wiki and the kickoff meeting already scheduled.”

4. Roles and groups with least privilege

The default roles are broad, and broad access quietly becomes a liability the moment a contractor joins. The agent builds tighter roles — a Contributor who edits work packages and logs time but cannot touch members or settings — maps your teams into groups, and applies the roles project by project so access matches reality instead of habit. Groups matter more than roles day to day: adding a new designer to one group beats clicking through fifteen projects to add them each time. The agent audits current access while it is in there and flags anything wider than it should be. Say: “Create a Contributor role that can edit work packages and log time but not manage members or versions, and give it to the Design group on all active projects.”

5. Notifications people will tolerate

The fastest way to lose a team is one email per comment. The agent reviews what triggers email versus in-app alerts, sets a daily digest as the default, keeps mentions immediate, and leaves per-user overrides intact so nobody’s careful setup gets flattened. Say: “Make sure nobody gets an email for every comment — only mentions and status changes on watched work packages — and set the default reminder to a daily digest.”

6. Brand the instance, honestly

Community OpenProject keeps its own branding, and full custom themes are an Enterprise feature — the agent will tell you that up front. What it can do is swap the logo image for yours and inject a small CSS override for the accent color, and it will say plainly which of those revert on upgrade and which properly need the Enterprise add-on later. Say: “Replace the OpenProject logo with ours and shift the accent color to our brand blue, and tell me what breaks on upgrade.”

7. Locale defaults that match the team

Language, first day of the week, date format — small things that silently annoy a distributed team for months. The agent sets the instance defaults so new users land in the right locale, and checks existing per-user overrides first so nobody’s settings get flipped mid-project. Say: “Set the default language to German for new users, make Monday the first day of the week, and don’t override anyone’s existing settings.”

8. Email that actually arrives

Notifications are useless in the spam folder, and self-hosted email is where most installs quietly fail. The agent points OpenProject’s SMTP at your mail provider, sets a From address that matches your domain’s SPF record so it passes receiving servers’ checks, sends test notifications, and inspects the headers. Say: “Point OpenProject’s email at our SMTP server with notifications@ourdomain as the From address, and send me a test mention so I can confirm it lands in my inbox.”

9. Harden the front door

A self-hosted app on the public internet gets probed daily. The agent forces HTTPS with a valid certificate, adds the standard security headers, rate-limits and fail2bans the login endpoint, and reviews which modules and API endpoints are exposed — then shows you the before and after instead of asking you to trust it. Say: “Lock the install down: force HTTPS everywhere, add security headers, and rate-limit the login page with fail2ban so password guessing gets boring fast.”

10. Watch the server so you don’t have to

Disk fills with attachments, the background worker queue backs up, the database stops answering — always at 6pm on a Friday. The agent sets up a daily health check that verifies the app responds, the database accepts connections, the job queue is draining, and disk headroom is healthy, emailing you only when something fails, plus log rotation so the evidence doesn’t get buried. Say: “Set up a daily health check of the app, database, worker queue, and disk space, email me only when something fails, and rotate the logs so they don’t fill the disk.”

See it in action

Official walkthroughs from the OpenProject team:

Worth a watch next:

• OpenProject installation on Ubuntu 20.04 — the official install walkthrough for the self-hosted plumbing this article customizes: HTTPS, SMTP, backups, and monitoring.
• OpenProject Invite and Manage Members — a short official guide to member and role management, the same screen territory as the least-privilege customization here.

Customization works best in small, explained steps. Ask for one change, look at the result, and let the agent write down what changed so the next person inherits the reasoning, not just the config. OpenProject on OpenSysLab