resolved
Okta
okta.com/admin/apps/active
landed in 38msBookSlash for Okta · IT
Identity admin,
one shortcut at a time.
Okta admin URLs are the kind of URLs IT teams keep in scratch documents. With BookSlash, the SSO config page, the MFA enforcement page, and the new-hire onboarding flow each get a memorable shortcut — and the audit log shows who changed what.
sso
other shortcuts you might save
b/ssob/mfab/new-hireb/scim
Suggested slug patterns
Steal these. They work for most teams.
Battle-tested shortcut conventions for Okta, with notes on why each one survives the URL changes that break personal bookmarks.
- b/sso
SAML SSO application list / config.
IT reviews it during every SaaS rollout. New engineers reaching for SSO setup land here directly.
https://{tenant}-admin.okta.com/admin/apps/active - b/mfa
MFA enforcement settings.
Security audits start at this URL. Saving it as a slug shortcuts the multi-click navigation.
https://{tenant}-admin.okta.com/admin/access/multifactor - b/new-hire
New-hire onboarding flow / group assignment.
Saved by IT as part of the onboarding checklist; HR opens it for every new hire.
https://{tenant}-admin.okta.com/admin/groups - b/scim
SCIM provisioning logs and status.
Debugging SCIM is a regular IT task; the URL is buried five sidebar levels deep.
https://{tenant}-admin.okta.com/admin/reports/sync - b/groups
Group memberships across the org.
IT and security review quarterly; managers request membership changes through this view.
https://{tenant}-admin.okta.com/admin/groups - b/logs
System log / audit log of identity events.
Security incident response always opens with this URL.
https://{tenant}-admin.okta.com/admin/reports/system-log
Common workflows
Three patterns that pay back in week one.
01
New-hire IT onboarding
Day-zero IT checklist starts at b/new-hire — the Okta group-assignment page that triggers SCIM provisioning across every connected SaaS tool. IT runs through the checklist, the new hire lands at b/wiki on day one.
02
Security incident triage
Suspicious sign-in alert? b/logs lands the security analyst on the Okta system log filtered by the affected user. The same slug works for SOC 2 evidence collection during audit windows.
03
Quarterly group review
b/groups becomes the standing URL for quarterly access reviews. IT, security, and managers all reach the same view; audit logs in BookSlash record every URL change.
With and without
Same Okta. Different team experience.
Without shortcuts
IT keeps a Notion doc of "useful Okta URLs" that nobody updates. Onboarding new hires requires a 15-minute walk-through of the Okta admin console. Security audits start with "where’s the system log?"
With BookSlash
b/sso, b/mfa, b/new-hire, b/scim, b/logs. Six shortcuts replace the Notion doc. IT, HR, security, and managers all reach the same URLs. Audit logs in BookSlash track every change.
Frequently asked
BookSlash + Okta
Yes — BookSlash supports SAML SSO via Okta on the Enterprise plan. Your IT team configures BookSlash as a SAML app in Okta; SCIM provisioning automatically adds and removes BookSlash users as Okta groups change.
Yes. Per-slug permissions let you scope edit access to specific roles (e.g., only IT admins can edit b/sso). The audit log records every change with timestamp and editor.
A wiki page is read-only and decays. BookSlash slugs are live URLs with redirect telemetry — you see who used b/mfa, when, and how often. The wiki was the documentation; the slug is the action.
You update the destination URL. End users keep typing b/sso; the new tenant URL takes over silently. Most IT teams script this as part of the migration runbook.
Start with one team. Roll out when it sticks.
Your stack. Your shortcuts.
One keystroke for everyone.
2,400+ teams reach every important destination in their stack with a single keystroke. Save the first slug in 30 seconds.
Free for personal use · No credit card · 14-day team trial