A user's session duration is the amount of time they stay logged in before logging them out, and they have to log back in. A session is idle when users don't interact with the product during that period of time. Interactions can be active (a user clicks a button) or passive (an open page auto-refreshes).
Before you can update the session duration, verify one or more domains. When you verify a domain, all the Atlassian accounts that use email addresses from the domain become managed by your organization. Learn about verifying a domain for your organization
What are authentication policies?
You set idle session duration in authentication policies. Authentication policies give you the flexibility to configure multiple security levels for different user sets within your organization. Authentication policies also reduce risk by giving you the ability to test different configurations for subsets of users before rolling them out to your whole company.
Set idle session duration with authentication policies
If you don't subscribe to Atlassian Access, you can set idle session duration in one authentication policy for all users. You need a subscription to Atlassian Access to take advantage of multiple authentication policies. Learn more about authentication policies
When you set idle session duration in an authentication policy, it only applies to your managed accounts. The setting doesn't apply to:
Accounts your organization doesn't manage
If you don't set idle session duration, we set a default duration of 30 minutes in the authentication policy. This applies to all the users who have access to your Atlassian products.
Navigate to Authentication policies at admin.atlassian.com.
変更するポリシーの [Edit (編集)] を選択します。
On the Settings page, select length of time for Idle session duration.
When you save changes to the session duration, users don't get logged out of their accounts. The new idle session duration will apply the next time a user logs in.