Skip to main content

​
Background

Last Login and Last Activity show whether users in Lumos may be overprovisioned, for example if they haven’t logged in for 90 or more days. Inactivity Workflows also use these fields to act on users who have not accessed apps in a set period of time. This article explains where Lumos sources this data.

​
Data sources

Lumos sources this data from a few places, notably:
  • Your IdP
  • Direct Lumos integrations
  • Manual uploads
The source controls where and how Lumos can pull Last Login/Activity.

​
Last Login

Wherever possible, Lumos populates this from the direct integration first, which will check the SaaS app directly to see when the user last logged into the system. If this data is not available, Lumos defaults to Last SSO Login, from your IdP (e.g. Okta). This has varying levels of accuracy, which depends on if you limit length of sessions, and thus require your users to log in on a regular cadence.

​
Last Activity

Today Last Activity is a column that is specially pulled via a direct Lumos integration; this will typically be a very granular, app-specific metric. For example, Lumos offers Last Activity for Zoom, which looks at the last time a user hosted a meeting of 40 minutes or longer. If you’re curious to see which applications have Last Login/Activity available via direct integration, see the Integrations Catalog.

​
FAQ

​
Why are there empty values?

In short, the integration that Lumos pulls last login from has never provided this data. In the case of Okta, Lumos looks at Okta system logs for login attempts, which Okta only stores for 90 days. When Lumos first discovers an Okta app, it checks for the last logins and shows the values in the table. An empty value means login never happened or it happened more than 90 days ago. The longer you use Lumos, the less important this becomes. Once Lumos sees a value, it caches it until it receives the next update. So if you use Lumos for 6 months, a “-” for Last Login for an Okta app means the user hasn’t logged in through Okta in 9 months (90+ days + 6 months since Lumos began syncing data with Okta).