QuuPass uses Cisco's official OAuth 2.0 Authorization Code flow to connect to your Meraki organization. You approve access directly in your Cisco dashboard — no API key is required and no credentials are ever shared with QuuPass.
Administrator or Full Organization Admin required
The Meraki account you authorize with must hold at minimum the Administrator role scoped to the organization you wish to manage. Network-only or read-only roles will cause the authorization to succeed but wireless write operations will be rejected by Cisco.
On the wizard start screen, click the blue Connect with Cisco Meraki button. QuuPass will generate a signed, time-limited state token and redirect your browser to Cisco's authorization server at as.meraki.com.
Cisco will ask you to sign in with your Meraki dashboard credentials. This happens entirely on Cisco's domain — QuuPass never sees your username or password.
Use the account that has Administrator (or higher) access to the organization you want QuuPass to manage.
Cisco will display the list of permissions QuuPass is requesting. These are the minimum required:
| Scope | Access |
|---|---|
dashboard:general:config:read | Read |
dashboard:general:telemetry:read | Read |
wireless:config:read | Read |
wireless:config:write | Write |
wireless:telemetry:read | Read |
See OAuth 2.0 & Permissions for a full explanation of each scope.
After you approve, Cisco redirects your browser back to QuuPass. The connection is confirmed with a green “Connected via Cisco Meraki” banner and you can proceed to Step 2 — Organization Selection. Tokens are refreshed automatically; you will not need to re-authorize unless you revoke access.
Once connected, you'll select the Meraki organization and network for your guest portal.