Connect your Okta tenant to Viio to pull a live user directory, surface real-world SSO activity, and discover every app behind the login button—so you can right-size licences and close shadow-IT gaps.
Capabilities
Capability | What Viio pulls from Okta |
✅ Users | Name, primary email, role, status, last-login time |
✅ Usage | Last SSO event per user and monthly sign-in counts |
✅ App Discovery | Full list of apps configured in Okta and their assigned users |
✅ App Usage | Sign-in counts per app and user, derived from System Log events |
Prerequisites
You must be an Okta Org or Super Admin (or a service account with equivalent rights) to create the API token.
Know your Okta base URL (for example,
acme.okta.com).Best practice: create a dedicated service account so the token never gets deactivated when people change roles.
Setup
Go to Viio → Integrations and choose Okta.
Generate an API token in Okta:
Sign in to the Okta Admin Console as an Org/Super Admin.
Go to Security → API → Tokens.
Click Create Token, give it a name, then Copy the token value—this is the only time you’ll see it. help.okta.com
Back in Viio, click Connect Okta, paste the API token and enter your Okta domain (e.g.
acme.okta.com).Hit Save. Viio starts the first data sync—it usually finishes within 15 minutes.
Need to disconnect?
In Viio, open Installed apps → Okta → Remove. You can also revoke the token from Okta Admin Console → Security → API → Tokens.
Troubleshooting & FAQ
Symptom | Quick fix |
“Invalid token” on connect | The token was revoked or copied incorrectly. Create a new token and reconnect. |
403 “Forbidden” after sync starts | The token-owner lacks read access to users or System Log. Re-create the token with a Super Admin or service account. |
No usage / app data | System Log must be enabled (all paid Okta editions include it). Check retention settings and wait for the next daily sync. |
Data stopped updating | Tokens expire if unused for 30 days. Re-generate a token and reconnect. help.okta.com |
Technical details
Authentication – Viio sends the header
Authorization: SSWS <token>on every call. help.okta.comPrimary endpoints called
GET /api/v1/users– roster of all active and suspended users developer.okta.comGET /api/v1/apps– catalogue of apps plus user assignments developer.okta.comGET /api/v1/logs– System Log events for sign-ins and app activity developer.okta.com
Data cadence – Viio refreshes Okta data daily
API calls respect Okta rate limits; Viio backs off automatically if limits are reached.
Additional resources
Okta API token management guide
Okta Users, Apps and System Log API references