1. Home
  2. Documentation
  3. Collecting data
  4. Signing in on Joripo Collect

Collecting data

Signing in on Joripo Collect

The three things a data collector types, approving a new phone, keys per workspace, keys that expire when a phone stops checking in, and moving to a new server address.

Joripo documentation · https://joripo.com/docs/collecting-data/joripo-collect-sign-in

On this page

Signing in

Joripo Collect asks for three things:

  1. Server name: your organisation's server name, for example riverbank-research. A manager can tell you what it is; it is shown under Configure › Server settings.
  2. Email or username: owners, managers and reviewers use their email address; data collectors usually have a username their organisation gave them.
  3. Password.

The app looks the server name up at the server address it knows. An organisation that runs its own Joripo server sets that address once under Server address in the app, by typing it or by scanning the QR code on the server's /app page. The app remembers the server name and the sign-in name, never the password.

A wrong password, an unknown person and an unknown server all get the same answer, so the sign-in screen cannot be used to find out who has an account. Too many wrong passwords block further tries for a while.

If the person's password was set by an owner and must be changed, the app says so: they sign in on the web once to choose their own, then sign in on the phone.

Without an account: a device key

Use a device key instead signs the app in with a device key's QR code, issued by an owner or manager on the workspace's field team page. A device key is not tied to a person; see Phones and device keys.

Approving a new phone

When someone signs in on a phone, the server registers that installation of the app for that person, and the phone appears under Joripo Collect devices on Collect, with the person, the phone's model, the app version and when it was last seen. Each organisation chooses a rule for new phones:

  • A person's first phone is approved at once, and any further phone waits for approval; or
  • every new phone waits for approval.

A waiting phone shows Waiting for approval and asks again by itself every few seconds. An owner or manager chooses Approve or Reject on Collect.

Owners' and managers' phones always wait holds every new phone of an owner or manager for approval, whatever the rule above, because their phones can download every preload file, and those often hold respondents' names. Another owner or manager approves it.

Which workspaces a phone gets

An approved phone receives one key for each workspace its person collects in: every workspace, unless an owner has chosen some for them. If the person has several, they choose one in the app and switch in Settings. Taking a workspace away from them stops that key at once, and the phone is told why; giving it back makes the same key work again.

Keys expire when a phone stops checking in

Joripo Collect checks in with the server when it opens and every ten minutes while it is used, and each check-in keeps its keys valid for another 30 days. A phone left unused or offline for 30 days is refused until it checks in again, which it does by itself the next time it is opened online. Nothing on it is lost, and what it could not send goes out then. A lost phone therefore stops working by itself after a month, even if nobody revokes it.

The app lock

If the server's device configuration turns on the app lock, the app asks for the account's password whenever it is opened. The check is made on the phone against a salted hash it keeps, never the password itself, so it works offline.

Signing out

Settings › Account and server › Sign out stops that phone's keys on the server at once. Drafts and finalized forms not yet sent stay on the phone, and go out once someone signs in on it again.

When the server's address changes

A server run from a laptop through a quick tunnel gets a new public address each time it starts. Phones signed in to Joripo Collect keep everything: in the app, open Settings › Server address, type the new address or scan the QR code on its /app page, and choose Use this address. The app checks that the new address is the same server (by its identity, not its address) before it moves its keys there. ODK Collect phones need a new device key.

Announcements

Messages the server's maintainer publishes for your organisation appear in the app as well as in the console, until they end or the person dismisses them.