Collect Menus, Settings, and Security

General Settings

To access General Settings:

⋮ ‣ General Settings

General settings

Server Settings

Server settings configure the connection to an OpenRosa server (Central, etc) or a Google Drive account.

To access Server Settings:

⋮ ‣ General Settings ‣ Server

Server settings

User Interface Settings

User Interface settings control Collect's appearance and behavior.

To access User Interface settings:

⋮ ‣ General Settings ‣ User Interface

User Interface settings

Theme

Toggles Light and Dark themes.

New in version 1.15.

The main menu, with the light theme enabled. The main menu, with the dark theme enabled.

Language

Forces the Collect interface to use a specific language. By default, Collect matches the device language. Note that this only sets the language for the Collect interface and not for form contents. For multi-language forms, the form language is set while filling out that form. The Collect translations are provided by the ODK community through the Transifex service. You can join Transifex to add or correct translations in your language.

Text font size

Sets the size of fonts used in the form-filling interface.

Splash Screen

Sets an image to display while Collect loads.

Maps Settings

Maps settings configure the maps shown by the location question types.

To access Maps settings:
⋮ ‣ General Settings ‣ Maps

Note

Prior to ODK Collect v1.23, map settings were available in the User Interface Settings. The basemap was configured by first selecting a Mapping SDK and then a Basemap.

Basemap settings

Basemap settings configure the background of maps shown by the location question types. Basemaps are provided by several different Sources which may each make several different map Styles available. A basemap is intended to provide details that help users orient a map and to make the map easy to use in a particular data collection environment. For example, if the data to be collected relates to elevation, consider selecting a topographic basemap.

Sources

A basemap source provides one or more map styles:

Reference layer settings

Reference layer settings configure map data shown on top of the basemap. Currently, a reference layer can only be defined by an offline MBTiles file as described in Using Offline Maps. The reference layer will appear when the zoom level is within the range supported by the file. If a reference layer has no transparency, it will fully cover the basemap selected above and behave like an offline basemap. Vector MBTiles files will only be available in the Layer data file menu if a Mapbox basemap is selected. Raster MBTiles files will be available for any basemap source and style.

Form Management Settings

Form Management settings control default behavior when editing, finalizing, and importing forms.

To access Form Management settings:

⋮ ‣ General Settings ‣ Form Management

Form Management settings Form Management settings

Form update

Blank form update mode

Specifies how blank forms should be updated:

Manually
The default mode in Collect. Enumerators manually manage blank forms on the device using Get Blank Form and Delete Saved Form.
Previously downloaded forms only
Enumerators will receive a notification when one or more forms on the device have an update available to their form definition or media files. Tapping on the notification will go to Get Blank Form where the user can choose to download some or all of the updated forms.
Exactly match server
Collect will automatically download and update forms based on what's on the server. In addition, forms not on the server will be deleted from Collect. This mode hides Get Blank Form and the Blank Forms tab in Delete Saved Form as they are not required. The enumerator can trigger an update from the server on the Fill Blank Form screen. Filled instances of blank forms deleted during server updates will still be editable.

Tip

If your server is configured to provide the exact set of forms enumerators need and you'd like to ensure they always have the most up to date versions on device then we'd recommend using Exactly match server.

However, if your server is set up to provide forms that aren't relevant to every enumerator then we'd recommend using Previously downloaded forms only (ideally with Automatic download) so that enumerators are still notified when the forms they do use are updated.

Manually makes the most sense when forms only need to be downloaded once and will never change or if you are extremely bandwidth-limited.

Automatic update frequency

Specifies how frequently Collect should check for updates to the forms on the server when using Previously downloaded forms only or Exactly match server. This option is not available if Manually is selected.

Automatic download

Only available if Previously downloaded forms only is selected. When Automatic download is enabled, the form update check will trigger an automatic download of any forms on the device that have updated definitions or media files. The user will receive a notification when the automatic download completes with either a success or failure. Tapping on the notification will go to Get Blank Form where the user will see success or failure messages for each form for which an update was attempted.

Hide old form versions

When enabled, if there are multiple versions of the same form, only the most recently downloaded will be displayed on the Fill Blank Form screen.

Form submission

Auto send

When enabled, forms are sent immediately when they are finalized, if the device can connect to the internet. If an internet connection is not available at the time of finalization, your finalized forms will be queued to send as soon as connectivity is established. You can specify whether to send over WiFi, cellular data, or both.

Delete after send

When enabled, form instances are deleted once they are sent.

Form filling

Default to finalized

When enabled, records are set to be finalized when saved at the end of a form-filling session. You can opt out of this at the end of filling any specific record. This is particularly important to consider when using encrypted forms because encryption happens on finalization. Finalized records for encrypted forms can't be opened because they are encrypted. Records for encrypted forms that have not been finalized are not encrypted and can be edited.

Constraint processing

Sets when form responses are validated against constraints.

Options:

  • Upon forward swipe. (That is, right after the question is answered.)
  • At finalization.

High res video

When enabled, Video widgets widgets will record high resolution video if possible.

Image size

New in version 1.11.0.

Sets the default maximum size for images added to forms, as measured by the number of pixels on the longest edge. Images larger than the maximum are scaled down immediately after being added.

Options:

Original size from camera (default)
Images are unchanged when added to a form. Recommended for use only when images must contain a lot of detail and when the internet connection used to send submissions is fast.
Very small (640px)
Recommended when images don't need to be detailed or the internet connection used to send submissions is slow.
Small (1024px)
Sufficiently detailed for most on-screen viewing but too small for printing.
Medium (2048px)
Sufficiently detailed for most uses, including printing.
Large (3072px)
Recommended when a lot of detail is needed, but you want to reduce the size of image files as much as possible.

Show guidance for questions

Guidance hints on questions can be used to display additional information that is not always needed. For example, they can be used to show extra instructions to be used during training or valuable only on a printout. If set to Yes - always shown, guidance hints will always be displayed below regular hints. If set to Yes - collapsed, the user will need to tap to view guidance hints.

Form import

Finalize forms on import

When enabled, forms added directly to the instances/ directory are automatically set to Finalized. This is particularly relevant when putting records for an encrypted form directly to the device because encryption happens on finalization.

User and Device Identity Settings

User and device identity settings control how personally identifiable information and device ID are used.

To access User and device identity settings:

⋮ ‣ General Settings ‣ User and device identity

User and Device Identity Settings

Form metadata settings

Form metadata settings control identifying information added to forms filled on the device.

To access form metadata settings:

⋮ ‣ General Settings ‣ User and Device Identity ‣ Form Metadata

Form Metadata Settings

User-defined

You can edit the following:

  • Username
  • Phone number
  • Email address

Note

Device-defined

You cannot edit these:

  • Device ID
  • Subscriber ID
  • SIM serial number
  • Install ID

Device ID is currently set to the device IMEI. Starting in August 2020, Google will no longer allow Android applications to read the IMEI. At that time, the Collect-generated Install ID will be used as the Device ID. Both are currently displayed to allow organizations to transition over. Install ID can be copied by long-pressing on its text.

Usage data

When enabled, ODK Collect sends anonymous usage and error data back to the ODK development team, which helps us improve the application.

Admin Settings

Admin settings manage other settings and features, letting you import or export settings, reset settings and delete cached data, and restrict which features are available to users of the app.

Admin settings are useful when you are managing devices that will be used by many enumerators, and you would like to limit the options available to those enumerators.

You can password protect the Admin setting screen, so enumerators cannot adjust settings or access restricted features.

To access Admin settings:
⋮ ‣ Admin Settings
Admin settings menu
General Settings
Provides access to General Settings, with all items unrestricted.
Admin Password
Lets you password protect this screen.
Reset application
Lets you reset to default settings, delete forms, and empty caches.
Import/Export settings

See:

User Access Control Settings

Main Menu Settings
Displays a list of Main Menu features. To hide features, uncheck them.
User Settings
Displays a list of user settings and other features accessible in the General Settings screen. To hide features, uncheck them.
Form Entry Settings

Displays a list of features related to viewing and filling out forms. To disable features, uncheck them.

Moving backwards

If you disable moving backwards, the enumerator cannot use the back button or swipe right to move backwards through a form.

However, disabling this feature does not completely restrict a user's ability to access already-answered questions. So, when you uncheck this box to restrict backward movement, the app will suggest several additional restrictions which will prevent a non-admin user from revisiting already-asked questions:

  • Disable Edit Saved Form option in the main menu
  • Disable Save Form option in the Form entry menu
  • Disable Go To Prompt option in the Form entry menu
  • Set Constraint processing to validate upon forward swipe in the Form Management settings
Image showing message displayed to configure other settings when Moving backwards option is unchecked.

Select YES to set these additional restrictions.

Note

When you enable the moving backwards option, you have to configure the other changed settings since they are not automatically changed back.