What each setting does
In the browser, an idle session also signs out after 15 minutes, or after your idle timeout if that is shorter.
When a change takes effect
- New sign-ins are judged by the new policy straight away.
- Sessions already open are judged at their next renewal, so a member can keep working for up to 15 minutes after you tighten the policy.
- OAuth grants made by a person, such as a CLI login, are judged when consent is given and at every token refresh. If the way that person signed in no longer satisfies the policy, the grant ends and they need to sign in again. Maximum session length and idle timeout don’t apply to these grants; their lifetime comes from the OAuth client’s token settings.
- API keys and machine credentials aren’t people and don’t sign in, so this policy doesn’t apply to them.
What your members see
A refused sign-in or session names the workspace and says why:
Magic links: asking for a link always gets the same response, so nobody can use that request to learn your workspace’s policy. If magic links aren’t allowed, the refusal appears when the link is opened.
Members of more than one workspace
A session that isn’t tied to one workspace is held to the strictest rules of every workspace the person belongs to, so the weakest workspace can’t be a way into the strictest.- SSO sessions are always tied to one workspace. So someone who belongs to a workspace that requires SSO signs in to it through its SSO, and to their other workspaces at each one’s own address.
- If their workspaces allow different methods with none in common, they see: “Your workspaces allow different sign-in methods, with none in common. Sign in to one workspace at a time, at its own address.”