Some changes to LimeSurvey are one-time setup jobs that pay off every single day after: the look, the security posture, the shape of your data. Your agent can do them in an afternoon, explain what it changed, and leave the configuration documented on the server. Here are ten worth asking for.

1. Make the Survey Look Like Your Brand

The default LimeSurvey theme is fine for testing and obviously generic in front of customers. The agent can copy the stock theme, swap in your logo, colors, and fonts, adjust the layout in the theme files, and strip the LimeSurvey credit line — without touching the original, so upgrades stay painless. It previews the result across screen sizes before handing it back.

Say: “Brand the customer survey with our navy and orange, put our logo in the header, and remove the LimeSurvey footer text.”

2. Package a Reusable Company Theme

One branded survey is nice; every survey starting branded is better. The agent can package your theme as a proper LimeSurvey theme archive with a clean name and version, set it as the default for new surveys, and keep the source files tidy on disk so future edits are a chat message away. This is also the moment to document which file controls what, for whoever asks next.

Try: “Turn my branded theme into a proper theme package called Acme Surveys, make it the default for every new survey, and show me where the files live.”

3. Fix How Hard Questions Actually Render

Some question types need polish before respondents can use them comfortably: slider labels that are invisible, array tables that overflow on phones, ranking questions that are fiddly on touchscreens. The agent edits the theme CSS and JavaScript, then tests on mobile viewport sizes and with real test responses. Small rendering fixes routinely lift completion rates more than question rewrites do.

Ask: “Make the slider question show its number while dragging, and fix the array question so it scrolls horizontally on phones instead of breaking the layout.”

4. Add a Small Custom Plugin

When the admin screens run out, plugins take over: prefilling answers from URL parameters so a respondent’s name and order number arrive already filled in, or pushing each new response to an external webhook the moment it is submitted. The agent can write the plugin, drop it in the plugins directory, enable it, and show you the event log proving it fires.

Try: “Write a plugin that prefills the email question from a ?email= URL parameter on the public survey link.”

5. Lock Down the Admin Panel

LimeSurvey’s admin area is the crown jewels — every response and participant email lives behind it. The agent can add a basic-auth prompt in front of /admin, restrict access to your office IP in the web server config, turn on fail2ban for failed logins, and confirm registration of new admin users is off. Layered like this, a leaked password alone is not enough to get in.

Say: “Restrict the LimeSurvey admin panel to our office IP, add basic auth on top, and set up fail2ban to ban after 5 failed logins.”

6. Separate Editors From Exporters

Not everyone with a login should walk away with the raw data. The agent can create user groups with tight permissions — people who can build and edit surveys but cannot export responses, others who can view statistics only — and audit the superadmin list for accounts nobody remembers creating. Principle of least privilege, applied to the one system that holds your respondents’ trust.

Ask: “Give the marketing team permission to edit the two customer surveys but not export data, and give finance read-only statistics access.”

7. Get Invitation Mail Out of the Spam Folder

Invitation deliverability lives in three places: the SMTP relay LimeSurvey sends through, the sender identity on your templates, and SPF/DKIM records on your domain. The agent can wire a proper SMTP relay into the config, fix sender names and reply-to addresses across your templates, run a test send, and tell you exactly which DNS records your mail provider needs. This is the highest-leverage fix on the list.

Try: “Send all LimeSurvey mail through our SMTP relay, set the sender to surveys@ourdomain.com, and tell me exactly which SPF and DKIM records to add.”

8. Prove Your Backups Actually Work

A backup you have never restored is a hypothesis. The agent can set up a nightly dump of the LimeSurvey database plus the uploaded files and config, rotate 30 days of copies to a second location, and run a monthly restore test into a scratch database to prove the dump is readable. If the restore test ever fails, you find out on the first of the month, not the day you need it.

Say: “Back up LimeSurvey every night at 2 AM, keep 30 days, send the copy off-server, and do a test restore on the first of each month with a report.”

9. Make Export Data Read Like a Spreadsheet

Default question codes look like Q1, Q2, SQ001 — meaningless in a CSV header six months later. The agent can rename codes to real names (satisfaction_nps, delivery_speed), enforce one naming convention across every survey, align scales so a 5 always means the good end, and clean unused token attributes. Your exports arrive analysis-ready, and trends across surveys stay comparable.

Ask: “Rename all question codes in the customer survey to descriptive names, and audit every survey so a 5 always means the most positive answer.”

10. Tune the Server Under the Survey

When a survey goes out to ten thousand people at once, small server settings start to matter: PHP memory limits, upload size for file questions, the timezone so timestamps match your business, session handling under concurrent respondents. The agent reviews the configuration end to end — web server, PHP, LimeSurvey’s own settings — and fixes the defaults that bite during big sends.

Try: “Check the server settings for a 10,000-invitation send next week — PHP limits, timezone, upload size — and fix whatever would fail under load.”

See it in action

Official walkthroughs from the LimeSurvey team:

Worth a watch next:

• LimeSurvey Tutorial – Question Type: Array — how array questions work, useful when tuning themes and rendering for complex question types.
• LimeSurvey Tutorial – How to set up an account and a survey installation — the official setup walkthrough that pairs with one-time installation jobs.

Do these once and your surveys start faster, look sharper, and leak nothing. LimeSurvey on OpenSysLab