/
How quickly do new SaaS appear in the Push admin console?
Push uses an API integration with your work platform as well as a browser extension deployed to employees to provide full visibility of the cloud accounts and apps in your environment.
Here’s how quickly you can expect to discover cloud identities and apps with these two methods.
After completing an API integration with your identity provider and assigning employee licenses, you’ll immediately see:
Social logins to SaaS apps.
MFA registration data for your primary work platform(s).
If using Okta, a list of your known Okta SSO apps and the accounts associated with them.
After the initial integration, Push checks once an hour to update this data in the Push admin console.
After enrolling employee browsers using the Push browser extension, you’ll see the following data types as soon as Push observes the login or signup:
Username / password logins for SaaS apps.
Login method for apps (OIDC, SAML, Okta SWA, password) and the associated identity provider.
Whether an account is shared among employees.
Whether a password is weak, reused, or leaked; uses words restricted by an administrator; or is manually typed (and unlikely to be using a password manager).
The user's browser version and when the extension last checked in for that employee.
For apps where Push supports MFA detection, you’ll see MFA data as soon as an enrolled employee visits the app.
If you are not seeing an app that you expected, verify that it’s supported by Push. Apps that Push does not yet recognize as work apps will appear in the "Other apps" section of the admin console. You can request support for an app to appear in your main SaaS inventory.
If you need any help troubleshooting why an app isn’t showing up, please contact us.