Overview
To ensure accurate app usage reporting in Tropic, it's important to configure session timeouts for third-party applications like Okta. Shorter session durations help provide precise active user counts by ensuring users are only marked as "active" while they are actively using an app. This also enhances security by reducing the risk of unauthorized access.
👉 You can view “Employees with Access” and “Active Employees” in the Suppliers Page by enabling these columns. For more details, see Viewing Employee Supplier Usage.Â
Understanding Session Timeouts
A session timeout is the period during which a user is considered "active" in an app without interaction. Shorter session timeouts provide more accurate user counts and enhance security by reducing the risk of unauthorized access. Note that some applications may not allow session timeout adjustments
Setting Session Timeouts
To adjust session timeouts for better accuracy and security, refer to the following links for specific instructions on configuring timeouts for various popular apps:
App | Link to instructions |
---|---|
Adobe | Configure the session timeout value |
Asana | SAML session timeout |
Atlassian | Update idle session duration |
Cloudflare | Manage active sessions |
DocuSign | Account Security |
Figma | Set an idle session timeout |
Fivetran | Authentication config |
FullStory | Inactivity Timeout Settings |
Google Workspace | Set session durations |
KnowBe4 | Session Limits and Settings |
LaunchDarkly | Configuring session length |
Looker | Session Duration |
Lucidchart | Configure idle session time-out limit |
Miro | Idle Session Timeout |
Monday | How to set a session duration on your account |
Outreach | Sign-in and password options |
Salesforce | Configure Session Timeout Settings |
Slack | Manage session duration |
Zendesk | Setting an inactivity time-out period |
Zoom | Changing account security settings |