To configure a Connection in Gundi with EarthRanger as a destination, you'll need either an access token (created by an EarthRanger admin) or a username and password. Either way, the credentials belong to an EarthRanger user (a token is always tied to one too), and that user needs the appropriate permissions to receive the movement and/or event data from the Connection.
Every EarthRanger site comes with a default user named “Gundi Service Account”, created specifically to support most flows between Gundi and EarthRanger. For most integrations, we recommend using this account; it already has the permissions needed for common telemetry and event workflows, so you don't have to configure anything yourself.
Before using it, review the Caveats section below for a few important exceptions where you'll need a different account or additional permissions.

Caveats
Keep in mind a few important limitations before you use the special “Gundi Service Account” user to receive data from Gundi.
- For “EarthRanger to EarthRanger” and other more complex integrations (e.g., integrations creating Event Categories and Event Types), we strongly recommend not using the “Gundi Service Account”, and instead, create a new service account with very specific permissions to what you need (e.g., Subject Group or Event Category). We recommend learning how to create and configure Service Accounts in EarthRanger to configure correct permissions for these integrations.
- For integrations pushing Event data, it's very likely that the “Gundi Service Account” user does not, by default, have permission to the Event Category that parents the Event Type used by the integration.Please update the “Gundi Service Account” user and assign the appropriate permission or permissions to grant access to that Event Category.
For example, if an integration sends weather alerts to an Event Type under a "Weather Alerts" Event Category, you'd grant the “Gundi Service Account” the "View Weather Alerts Event Permissions" permission, as shown below.

Creating tokens in EarthRanger
As noted above, a Connection can authenticate to EarthRanger with either a username and password or an access token. A token is the more secure option: it's tied to a single EarthRanger user, carries only that user's permissions, and can be revoked without changing anyone's password.
If you plan to authenticate with a token, an EarthRanger admin needs to create one before you configure the Connection in Gundi. Make sure the user the token belongs to has the appropriate permissions for your integration.
For step-by-step instructions, see Create and Manage Authentication Tokens for Secure Integrations.
