Administering Aggregate

Click the Log In link in the upper right corner of the screen to be presented with the Log onto Aggregate screen. Choose the Sign in with Aggregate password button and enter the super-user username you specified within the installer. The initial password for this account is aggregate. When you log in, Site Admin will be visible to you.

Image showing sign in option.


  • When signing in with this method, if you do not enter the password correctly, you may need to close all your browser windows and quit your browser before you can try again.
  • If the instance name of the server changes (the installer asks for this name), then the passwords for all ODK Aggregate usernames will be cleared (preventing their use) and the super-user username's password will be reset to aggregate and the above message will also be displayed. In this case, you should log in, change the super-user's password, and change the passwords for all of your ODK Aggregate usernames.
  • In April 2015, the use of Google e-mail accounts for accessing the site (via Sign in with Google) stopped working (Google turned off that functionality). If you have an existing site running an old version of ODK Aggregate that does not have ODK Aggregate usernames configured for website access (and offers a Sign in with Google sign-in choice), you will need to upgrade to regain access to it.


Beginning with ODK Aggregate 1.3.2, upon the initial installation of the server, it is configured to allow unauthenticated (anonymousUser) submissions from ODK Collect and unauthenticated browser access to the submissions and forms management functionality of ODK Aggregate.


If you have not yet changed your super-user password to something other than the default password of aggregate, the server will display a warning at the top of the web page.


If you do not change the default password, anyone can take complete control of your server!

Image showing server not secure warning.

Please visit the Permissions sub-tab under the Site Admin tab to change this user's password.

Image showing permissions sub-tab.

You can specify additional usernames with browser access to the server under the Permissions sub-tab. Privileges are as follows:

  • Data Collector: able to download forms to ODK Collect and submit data from ODK Collect to ODK Aggregate.


  • Only ODK accounts and the anonymousUser can be granted Data Collector rights.
  • The anonymousUser must be granted Data Collector rights to accept submissions from unidentified sources (e.g., from ODK Collect 1.1.5 and earlier, or from ODK Collect 1.1.7 and later if not authenticating).
  • Data Viewer: able to log onto the ODK Aggregate website, filter and view submissions, and generate csv or kml files for download.
  • Form Manager: all the capabilities of a Data Viewer plus the abilities to upload a form definition, delete a form and its data, and upload submissions manually through the ODK Aggregate website.
  • Site Administrator: all the capabilities of a Form Manager plus the ability to add users, set passwords, and grant these capabilities to other users.
Image showing privileges.

Remember to click Save Changes to make these changes take effect. You can also edit the privileges for current users.

You can upload a .csv file of users and their capabilities as well as download the current file.


In the Preferences sub-tab under Site Admin tab, you can manage:

  • Google API credentials: These credentials are used when publishing into Google services. For details on this, see Aggregate OAuth2 info.
Image showing google api option.
  • Enketo credentials: These credentials are used for Enketo webforms integration. To link Enketo with Aggregate, see this.

  • ODK 2.0 App name

    • ODK Tables Synchronization Functionality - check this to enable ODK Tables functionality to download, upload and alter data records within ODK Tables as restricted by table-access privileges granted to the user.
  • Aggregate features: These settings affect the operations of the server.

    • Disable faster background actions - check this to reduce App Engine quota usage.
    • Skip malformed submissions - check this to ignore corrupted submissions.
Image showing other options.