Because QuuPass connects to Meraki using OAuth 2.0, your organization is determined by the Meraki account you authorised in Step 1. There is nothing to choose — QuuPass reads the organization directly from your OAuth connection.
When you completed the OAuth authorization in Step 1, you granted QuuPass access to your Meraki account. QuuPass uses that access token to identify exactly one organization — the primary organization associated with that Meraki admin account.
On this screen you will simply see your organization name displayed and a Continue button. No selection is required.
QuuPass is designed for a single-organization deployment per account. If the Meraki admin account you authorized belongs to multiple organizations, only the first organization returned by the Meraki API will be used.
If this is not the organization you intended to use, you will need to revoke the current OAuth connection and reconnect using a Meraki admin account that is scoped to the correct organization. See Wrong organization? below.
If the organization displayed is not the one you want to use, this means the Meraki account you connected in Step 1 is linked to a different organization. To fix this:
Confirm your organization looks correct, then click Continue to move to Step 3 where you will select the specific Meraki network (site) to connect to.