LimeSurvey survey lifecycle

On survey activation, the plugin provisions the Ramon survey and enables it by default. Repeating provisioning is idempotent: the same LimeSurvey instance and survey retain their Ramon survey ID while the title and version metadata update.

Use the survey-level Ramon menu to view provisioning state, the configured survey name, mapped responses, and the explicit enable/disable setting.

Opt-out and retries

Disabling Ramon from the survey’s Ramon page is an explicit opt-out. A later LimeSurvey reactivation will not silently re-enable it.

Ramon service failure does not block survey activation or title editing. The plugin records provisioning or title synchronization as pending and retries it through LimeSurvey's native plugin cron event. Configure your normal LimeSurvey cron runner so those retries can execute.

Participant identity

The plugin emits a random Ramon UUID in a plugin-owned hidden field and records the mapping in its own table. It does not add or modify a LimeSurvey answer column. No survey answers, participant attributes, LimeSurvey tokens, or private organization key are sent to Ramon.