Okta Unbound

Group, user & rule management for Okta admins — bulk ops, rule-impact analysis, and local audit logging.

Okta Unbound is a Chrome side panel for Okta administrators who need more than the admin console gives them: why a person has the access they have, who is really in a group, what a group rule will do before it runs, and a way back from what you just changed. It runs alongside the Okta admin session you already have open. No separate login, no API key, no server in the middle. BETA: This extension is still in beta and has features that may contain bugs. Use caution taking destructive action on a production org. You are responsible for your own use of this extension. WHAT IT DOES Users — Look up anyone and see every group they belong to, with each membership traced to its source: a rule that matched them, or a direct assignment. Read the full profile, edit attributes, suspend or unsuspend, or trigger a password reset. Groups — Search with combined live and cached results, filter by type and size, and open a group to see its members, where each member came from, and an MFA coverage scan across the whole membership. Rules — Read a group rule the way Okta evaluates it, clause by clause, against a real person, so a rule that looks right and behaves wrong stops being a mystery. Predict what a change would affect before you make it, and catch conflicts between rules. Apps — See which users and groups can reach an application, and whether that access is direct or inherited through a group. Policies — Read the authentication policies that decide what sign-in requires, and for whom. Read-only. Export — CSV for users, groups, memberships, group rules, apps, app assignments, authentication policies, devices, network zones, SAML identity providers, and org reports. Choose the scope, choose the columns, take the evidence with you. History — Every change the panel makes is recorded locally, with an undo for the ones that can be reversed. Selection — Tick users and groups from anywhere in the panel, then act on all of them at once. Command palette — Cmd K, or Ctrl K, to reach any tab, group, or user. Home — A snapshot of the org and the entities you have been working with. A full user guide, with every feature shown as it actually looks: https://samdhenderson.github.io/Okta-Unbound/guide/ PRIVACY AND SECURITY - No data is collected, transmitted, or shared with the developer, an analytics service, or any third party. No telemetry, no tracking. - The only network requests are between your browser and your own Okta org. - No credentials or API keys are stored. The extension uses your existing signed-in session, and the session token is read from the page per request and never persisted. - Password and recovery-question fields are stripped before any code sees them and can never be written through the extension. - Cache, preferences, and history are stored locally in chrome.storage.local and IndexedDB. Some of that is tenant personal data: the action history keeps the affected user's email and the before and after values of edited attributes, because that is what makes undo possible. It is capped at the newest 50 actions and can be cleared at any time. - Full detail, including retention and how to remove everything, is in the privacy policy. WHO IT IS FOR Okta administrators who manage enough groups, users, and rules that the admin console stops scaling: bulk membership work, tracing access to its source, predicting the blast radius of a rule change, and getting evidence out as CSV. HOW IT WORKS The side panel talks to the Okta admin tab you already have open. A content script running on Okta domains reads the page for the session token and the entity you are viewing, and every API call goes directly from your browser to your Okta tenant. Nothing passes through an intermediary server. Requests are rate limited and scheduled so a bulk operation does not exhaust your org's API budget. Two judgment calls worth flagging: I described Apps, Rules and History without claiming detail pages they don't have yet (status.ts marks all three in-progress), and I kept Policies explicitly read-only. If you'd rather the listing not point at the user guide until you've looked at it live, drop that one line.