Skip to content

Commit f557199

Browse files
authored
Update content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md
1 parent 5811b9a commit f557199

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ If someone sets the default idle timeout to 90 minutes in their personal setting
3434
3535
### Setting organization-wide and repository-specific policies
3636

37-
When you create a policy you choose whether it applies to all repositories in your organization, or only to specified repositories. If you create an organization-wide policy with a timeout constraint, then the timeout constraints in any policies that are targeted at specific repositories must fall within the restriction configured for the entire organization. The shortest timeout period - in an organization-wide policy, a policy targeted at specified repositories, or in someone's personal settings - is applied.
37+
When you create a policy, you choose whether it applies to all repositories in your organization, or only to specified repositories. If you create an organization-wide policy with a timeout constraint, then the timeout constraints in any policies that are targeted at specific repositories must fall within the restriction configured for the entire organization. The shortest timeout period - in an organization-wide policy, a policy targeted at specified repositories, or in someone's personal settings - is applied.
3838

3939
If you add an organization-wide policy with a timeout constraint, you should set the timeout to the longest acceptable period. You can then add repository-specific policies that set the maximum timeout to a shorter period.
4040

0 commit comments

Comments
 (0)