Document Strict UI Session Mode

[LutaoX]

Summary

• Add Strict UI Session Mode as the final identity and access management control on the Cloud security controls page.
• Document the 15-minute inactivity limit, 12-hour maximum session, SAML prerequisite, scope, enablement, and limitations.
• Link to the guidance from the Account access introduction.
• Add links to the existing SAML and SCIM references in the Account access introduction.

Why

Strict UI Session Mode is approaching GA but has no public documentation. Customers need to understand what sessions it affects, how inactivity is measured, and how to request enablement.

Test plan

• Confirm the new section renders under Identity and access management at /best-practices/security-controls#restrict-cloud-ui-session-lifetimes.
• Confirm the Account access page links to the new section, SAML, and SCIM.
• Confirm the SAML, support ticket, Account Id, and related internal links resolve.

Validation

• Branch created from the latest temporalio/documentation main.
• git diff --check passes.
• Local Vale is unavailable; PR CI runs the repository Vale gate.

Made with Cursor

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
temporal-documentation	Ready	Preview	Sep 11, 2026 7:32pm UTC

[github-actions]

📖 Docs PR preview links

• Best Practices
  • Security controls for Cloud
• Cloud
  • Account access

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ec8a525d94

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Move session-mode operations into the Cloud access docs

Keep a brief best-practice recommendation here, but move the prerequisites, support-ticket procedure, scope, and timer behavior to a page under docs/cloud/manage-access/. The architecture guide assigns SAML and Cloud-specific operations to the Temporal Cloud section, while this 55-line addition adds four headings and takes the security-controls page from 16 to 20 headings, beyond the repository's target of fewer than 15 total.

AGENTS.md reference: AGENTS.md:L247-L253

Useful? React with 👍 / 👎.

[LutaoX]

Note the key reason for having this feature here is because the feature itself is for security control use cases and best practices rather than access management.
The target persona or market sector is governance sector, financial services that have stricter compliance and security policies and requirements to fulfill.

[github-actions]

📝 [vale] <Std.Abbreviations.Latin> _{reported by reviewdog 🐶}
Use 'for example' instead of 'e.g.'.

Suggested change

	Only Cloud UI activity that sends a request to Temporal Cloud resets the inactivity timer (e.g. create a Namespace). Mouse movement, scrolling, or reading information that has already loaded does not reset the timer.
	Only Cloud UI activity that sends a request to Temporal Cloud resets the inactivity timer (for example create a Namespace). Mouse movement, scrolling, or reading information that has already loaded does not reset the timer.