Sessions
Sessions sets how long people in your organisation stay logged in to the Strise web app. You can log people out after a period without activity, a fixed time after they log in, or both.
Where to find it
Open the account menu → Organisation → Sessions. The page appears for anyone whose role lets them view session limits, which the Organisation Admin role does. Only people whose role also lets them change the limits can edit them; everyone else sees them read-only.
The two limits
| Limit | What it does | Choices |
|---|---|---|
| Log out after inactivity | Ends a session after this long without activity. | 15 minutes, 30 minutes, 1, 2, 4, 8, or 24 hours, or 3 days |
| Maximum session length | Ends a session this long after logging in, however active it is. | 1, 4, 8, 12, or 24 hours, 3 days, or 7 days |
Both default to No limit, and each can be set back to No limit at any time. A change applies within about a minute, including to sessions that are already open.
Strise records each change in the organisation's Activity log, which Organisation admins can read.
What counts as activity
Clicking, tapping, typing, scrolling with the mouse wheel, and moving the mouse count as activity. Data the app refreshes on its own does not, so a browser tab left open does not keep a session alive.
Who the limits apply to
The limits apply to everyone in the organisation who uses the Strise web app. If someone belongs to more than one organisation, Strise applies the shortest limit among them.
The limits do not apply to API keys, the Connect API, or connected apps.
Strise applies its own limits on top: a session ends after 3 days without activity or 7 days in total, whatever your organisation sets. The limits on this page can make sessions shorter, not longer.
When a limit is reached
Strise logs the person out and shows Session expired, please login to continue. on the login page. When they log in again, a new session starts.
Related
Last updated on