You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Set session lifetime limits and sign out every member of your organization at once
4
+
---
5
+
6
+
import { FAQ } from'@/components/ui/faq'
7
+
8
+
Session Policies let organization owners and admins on Enterprise plans control how long member sign-in sessions last, and sign out every member org-wide in one action. Policies apply to every member of the organization on every device.
9
+
10
+
---
11
+
12
+
## Setup
13
+
14
+
Go to **Settings → Security → Session policies** in your organization settings.
15
+
16
+
Both limits are optional. Leave a field empty to keep the default behavior: sessions last 30 days and extend automatically while a member stays active.
17
+
18
+
---
19
+
20
+
## Settings
21
+
22
+
### Max session lifetime
23
+
24
+
Caps how long a session can exist from the moment a member signs in, regardless of activity. When the limit is reached, the member must sign in again.
25
+
26
+
Use this to enforce periodic re-authentication — for example, a value of `168` requires everyone to sign in again at least weekly. Accepts 1 to 8760 hours (1 year).
27
+
28
+
### Idle timeout
29
+
30
+
Signs a member out after this many hours without activity. Activity extends the session, so members who use Sim regularly stay signed in; dormant sessions expire.
31
+
32
+
Accepts 24 to 8760 hours. The 24-hour minimum exists because session activity is recorded at most once per day — a shorter window would sign out members who are actively working.
33
+
34
+
### Sign out all members
35
+
36
+
The **Sign out all members** action immediately revokes every member session in the organization except your own. Members are signed out on their next request — typically within a minute — and must sign in again.
37
+
38
+
Use this after a security incident, an offboarding wave, or before tightening a policy you want to take effect everywhere at once.
39
+
40
+
---
41
+
42
+
## How enforcement works
43
+
44
+
-**New sign-ins** get an expiry that respects the policy from the moment the session is created.
45
+
-**Existing sessions** are shortened immediately when you save a tighter policy — no member keeps a longer session than the new policy allows.
46
+
-**Loosening a policy never extends existing sessions.** Members pick up the longer limit the next time they sign in.
47
+
- Changes propagate to active members within about a minute; there is no need to redeploy or wait for sessions to naturally expire.
48
+
49
+
---
50
+
51
+
## FAQ
52
+
53
+
<FAQ
54
+
items={[
55
+
{
56
+
question: 'Do session policies apply to SSO sign-ins?',
57
+
answer:
58
+
'Yes. Sessions created through SSO follow the same lifetime and idle limits as any other sign-in method. Your identity provider may enforce its own, stricter session rules on top.',
59
+
},
60
+
{
61
+
question: 'What happens to a member who is working when their session expires?',
62
+
answer:
63
+
'They are redirected to sign in again on their next request. Unsaved workflow changes in the editor are preserved by the collaborative canvas, which continuously syncs edits.',
64
+
},
65
+
{
66
+
question: 'Does "Sign out all members" affect API keys or running workflows?',
67
+
answer:
68
+
'No. It revokes browser sign-in sessions only. API keys, deployed workflows, webhooks, and schedules keep working — manage those separately from the API keys settings.',
69
+
},
70
+
{
71
+
question: 'Why is the minimum idle timeout 24 hours?',
72
+
answer:
73
+
'Session activity is recorded at most once per 24 hours for performance. An idle timeout below that window could sign out members who are actively using Sim, so shorter values are not accepted.',
0 commit comments