SuiteCRM is built to be reshaped. Studio, Module Builder, layout editors, themes, dropdowns, and a config file you can actually read are all first-class parts of the product. The catch is that the reshaping tools assume you already know what good looks like. The agent reads your install before touching it and works in the upgrade-safe custom directory by default. These ten customizations range from one new field to a whole new module.
1. Add the fields your sales process is missing
Out of the box, an opportunity has no place to record the competitor you lost to or why a deal died. Custom fields fix that, and the agent does them properly: created through Studio, stored in custom vardefs, and placed on the edit, detail, and list views so people actually fill them in. New fields also become available to workflows and reports, which is usually the point. Try: “Add a Loss Reason dropdown to opportunities with our five usual reasons, show it on the edit and detail views, and add it as a column in the list view.”
2. Build a whole new module with Module Builder
Core modules cover sales and support, but not your world. An equipment rental shop needs an Assets module; a training company needs Courses. The agent defines the fields — asset tag, serial number, purchase date, status — builds the module in Module Builder, deploys and installs it through Module Loader, and adds it to the main navigation. A module that takes a consultant a day takes the agent an hour, and it shows you the module in a test record before calling it done. Try: “Build me an Assets module with tag, serial number, purchase date, status, and a photo field, and put it in the main menu.”
3. Wire up relationships and subpanels
A standalone module is a spreadsheet; relationships make it a system. The agent links your new module to the core ones — accounts own assets one-to-many, contacts custody them many-to-many — so the related records show as subpanels on both sides. It also sets which side of the relationship owns the record and keeps the join tables indexed, because a many-to-many that slows down list views is worse than none. Try: “Link Assets to Accounts one-to-many and to Contacts many-to-many, and show me on each asset who holds it and on each account what it owns.”
4. Get a real report, with a chart, on a schedule
The built-in Reports module is stronger than most people realize: grouped totals, conditions, charts, and scheduled email delivery as a PDF. Describe the question and the agent builds the report — say, open opportunities grouped by sales rep with a bar chart and a this-quarter condition — adds it as a dashlet, and sets a Scheduled Report to mail you the PDF every Monday. Try: “Build a report of open opportunities by rep with a bar chart for this quarter, and email me the PDF every Monday morning.”
5. Rebrand the look without breaking upgrades
The SuiteP theme ships with four subthemes — Dawn, Day, Dusk, and Night — and everything about the look can be overridden in a custom theme copy so the next update doesn’t wipe it. The agent switches the subtheme, replaces the login-page logo and favicon, adjusts navbar colors to your brand, and tells you which files it touched so future-you can find them. Try: “Switch us to the Night subtheme, put our logo on the login page, recolor the navbar to our brand color, and tell me which files you changed.”
6. Make quotes and invoices look like your company
Default PDF output screams “unconfigured CRM”. The PDF Templates module handles this: letterhead header image, your company details, the grouped line-item table, tax and totals layout, payment terms and bank details in the footer. The agent builds the template against a sample quote, renders it, and iterates with you on spacing until it looks like something you’d sign. Try: “Design a quote PDF template with our letterhead, our bank details, and thirty-day payment terms in the footer, and make it the default for new quotes.”
7. Open the customer portal and stock the knowledge base
The customer portal lets contacts log in, read your published answers, and file cases that thread directly into the Cases module — which cuts email tag by a third if the knowledge base has real content. The agent enables the portal, sets portal roles, publishes your top ten support answers as knowledge base articles, creates a test portal user, and files a case as a customer would so you see exactly what they see. Try: “Turn on the customer portal, publish these ten FAQs as knowledge base articles, and make a test portal user so I can file a case as a customer.”
8. Harden logins and permissions in one pass
Security in SuiteCRM is layered — HTTPS at the web server, security groups controlling who sees which records, roles controlling what they can do, password policy, and two-factor for admins. Most installs have drifted in all four. The agent forces the HTTPS redirect, turns on two-factor for admin accounts, sets a 12-character password policy, reviews every security group and role for gaps, and lists all users so you can spot ex-employees still holding keys. Try: “Audit my security: force HTTPS, enable two-factor for admins, enforce a 12-character password policy, and list every user with their roles so I can prune access.”
9. Lock down API access for your integrations
The v8 REST API is how external tools reach your CRM, and a full-access admin token in a reporting script is an accident waiting for a leak. The agent creates a dedicated API-only user, restricts its role to just the modules the integration reads, adds an IP allowlist for the API paths at the web server, and shows you the rotation procedure so the secret changes yearly instead of never. Try: “Create a read-only API user for our reporting tool, restrict it to accounts and opportunities, allow only our office IP to reach the API, and show me how to rotate the secret.”
10. Clean up the vocabulary your team reads all day
Defaults like “Opportunities” and “Cases” read like 2005. Rename Modules changes them everywhere — menu, labels, even existing data — and the Dropdown Editor lets you prune the lead sources and industries nobody uses, so dropdowns stop being a museum. The agent also adds dependent dropdowns where the base product can’t, like state filtered by country, with a small custom override. Try: “Rename Opportunities to Deals and Cases to Tickets everywhere, delete the lead sources we never use, and make the state dropdown depend on the selected country.”
See it in action
Official walkthroughs from the SuiteCRM team:
Worth a watch next:
- Adding Grouped Fields to the Record View — SuiteCRM 8 Tutorial — the official counterpart to reshaping record layouts like ideas 1 and 2.
- SuiteCRM 8: Overriding Config Values — config-level customization, the same layer the agent edits on your server.
Each of these lives in your files and your database, owned by you, on your server — not in a plugin marketplace or a vendor’s roadmap. The agent just does the part you’d otherwise read forty documentation pages for. See SuiteCRM on OpenSysLab and pick the first customization your team will notice.
