What changed: When you make incompatible changes to a case type (such as changing a field type), the system now creates a separate case type version. Old cases remain in the original version while new cases use the updated version.
Who is affected: App administrators who edit case type configurations.
Action required: After creating a new case type version, manually update FormSG webhooks, email forwarding addresses, API/Plumber/Opus integrations, workflows, role permissions, and filters to point to the new case type.
What changed: You can now share email drafts with other users in the same app. Shared drafts appear in the drafts list for all app users, who can view and edit them before sending.
Who is affected: All users with email correspondence permissions.
What changed: You can now use {{field_name}} syntax in email subject and body fields to dynamically insert case field values, matching the existing functionality in workflow email templates.
Who is affected: All users with email send permissions.
What changed: You can now configure granular permissions that restrict when specific roles can view or edit a case based on its current status, and restrict which roles can transition cases between specific statuses.
Who is affected: App administrators configuring roles and permissions.
Action required: No action required. This is an opt-in advanced feature enabled under Settings > Case Statuses > More Settings.
What changed: Tags can now be assigned to users (not just cases). User roles can be configured with permissions that apply only to cases matching the user’s tags, enabling granular case visibility restrictions.
Who is affected: App administrators who need fine-grained access control.
Action required: No action required. Enable the advanced feature under Settings > Tags > More Settings.
What changed: Common email notifications (new case assignment, cases exceeding duration threshold, new case comments, workflow errors) are now included by default. You no longer need to create workflows for these notifications.
Who is affected: All app users.
Action required: No action required. Configure notification preferences under your profile > Manage My App Notifications.
What changed: Three email parsing mechanisms (Paragraphs, Line by line, HTML) are now available to automatically fill case fields from the content of the first email received in a case.
Who is affected: App administrators configuring email-linked case types.
Action required: No action required. Select a parsing mechanism when editing the case type under “Automatically create new case upon receiving: Email Correspondence”.
What changed: Two sets of APIs are now available: Case Management API (case CRUD, search, file upload, email operations) and App Administration API. API documentation is available via Swagger.
Who is affected: Developers integrating external systems with Ownself Gather.
Action required: Generate an API key under Settings > API Keys to begin using the APIs. Default rate limit: 100 requests per 5 minutes per API key.
What changed: IM8 user declarations can now be performed annually instead of the previous monthly requirement. The frequency can be changed in app settings.
Who is affected: App administrators responsible for user access declarations.
Action required: No action required. To change frequency, navigate to Settings > User Declaration Frequency.
What changed: Outbound emails from Ownself Gather are now sent from @ownself.gather.gov.sg instead of @gather.gov.sg. Auto-forwarding rules using @gather.gov.sg for inbound email are unaffected.
Who is affected: All users sending emails from Ownself Gather apps.
Action required: No action required for auto-forwarding rules. If you have email filters based on the sender domain, update them to use @ownself.gather.gov.sg.
What changed: Gov.sg users whose accounts have been inactive for more than 90 days can now reactivate their own accounts at gather.gov.sg/support/reactivate-account without submitting a support ticket.
Who is affected: Gov.sg users with inactive accounts.
What changed: You can now duplicate an existing case to create a new case pre-populated with the original case’s field values, subject to field-level permissions.
Who is affected: Users with view and create case permissions.
What changed: The workflow builder now supports an advanced mode with if-else conditions, loops, custom scripting, and more complex logic beyond the basic mode’s linear actions.
Who is affected: App administrators building workflows.
Action required: No action required. Advanced mode is available when creating or editing a workflow.
What changed: Incomplete workflows can now be saved as drafts and resumed later. Draft workflows cannot be activated until all required steps are complete.
Who is affected: App administrators building workflows.
What changed: Workflow step 3 now allows you to define case field aliases outside of workflow actions, providing clarity when referencing fields in subsequent actions.
Who is affected: App administrators building workflows.
What changed: Ownself Gather now supports email correspondence within cases. New features include: creating cases from emails, sending/replying/forwarding emails from within cases, email read/unread tracking, email signatures, and filtering cases by email status.
Who is affected: All app users with email permissions enabled.
Action required: To use email correspondence: (1) enable email permissions for relevant user roles, (2) link your agency mailbox to a case type, (3) set up auto-forwarding rules in your mail client.
What changed: Users with email addresses from ITE and polytechnic domains (ite.edu.sg, moe.edu.sg, np.edu.sg, nyp.edu.sg, rp.edu.sg, science.edu.sg, sp.edu.sg, tp.edu.sg) can now create apps on Ownself Gather.
Who is affected: Staff at ITE and polytechnic institutions.
Action required: No action required. Whitelisted users follow the same login process as non-gov.sg users (Singpass authentication).
