Update description for AutomaticAppLogIn policy

[differsthecat]

🎟️ Tracking

https://bitwarden.atlassian.net/browse/PM-26720

📔 Objective

Update wording of the IDP auto-submit policy

📸 Screenshots

N/A

⏰ Reminders before review

• Contributor guidelines followed
• All formatters and local linters executed and passed
• Written new unit and / or integration tests where applicable
• Protected functional changes with optionality (feature flags)
• Used internationalization (i18n) for all UI strings
• CI builds passed
• Communicated to DevOps any deployment requirements
• Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

• 👍 (:+1:) or similar for great changes
• 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
• ❓ (:question:) for questions
• 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
• 🎨 (:art:) for suggestions / improvements
• ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
• 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
• ⛏ (:pick:) for minor or nitpick changes

[differsthecat]

Clients PR: bitwarden/clients#17118

[claude]

Claude finished @differsthecat's task —— View job

---

PR Review: Update description for AutomaticAppLogIn policy

Tasks

• Read and analyze the modified file
• Review the description change
• Provide comprehensive feedback

---

Summary of Changes

This PR updates the display name for the AutomaticAppLogIn policy in src/Core/AdminConsole/Enums/PolicyType.cs:48:

• Before: "Automatically log in users for allowed applications"
• After: "Automatic login with SSO"

Critical Issues

None identified.

Suggested Improvements

📝 Consider description clarity and consistency

The new description "Automatic login with SSO" is significantly shorter and mentions SSO explicitly, but it may be less descriptive than the original. Consider:

1. User clarity: The original description "Automatically log in users for allowed applications" was more explicit about:

   • What happens (automatically log in users)
   • Scope (for allowed applications)

2. SSO specificity: The new description ties this directly to SSO, which is accurate based on the linked clients PR context. However, ensure this aligns with how users understand this feature.

3. Verb tense consistency: Most other policy names in this file use noun phrases or imperative forms (e.g., "Account recovery administration", "Remove Send", "Vault timeout"). The new name "Automatic login with SSO" follows this pattern better than the old one, which used a full sentence with a verb.

Recommendation: The change is acceptable if it better reflects the actual functionality and aligns with user documentation. However, verify that:

• User-facing documentation is updated to match
• The shorter description doesn't cause confusion for administrators configuring this policy
• This aligns with the corresponding clients PR changes

🔍 Verify alignment with clients PR

The related clients PR (bitwarden/clients#17118) should have corresponding description updates. Ensure that:

• The terminology is consistent across server and clients
• Any UI tooltips or help text in the clients also reflect this wording change
• Documentation updates are coordinated

Reference: src/Core/AdminConsole/Enums/PolicyType.cs:48

Good Practices Observed

• Follows the guideline in the code comment: "Do not include the word 'policy' in the return value"
• Maintains consistency with the naming pattern of other policies
• Simple, focused change that addresses the stated objective

Action Items for Author

1. ✅ Verify the new description accurately reflects the policy's functionality
2. ✅ Confirm alignment with the clients PR changes
3. ✅ Ensure any user-facing documentation or help text is updated accordingly
4. ⚠️ Consider whether administrators will understand the scope of "Automatic login with SSO" vs. the more explicit original description

Security & Performance

• ✅ No security implications (display string only)
• ✅ No performance impact (compile-time constant)
• ✅ No cryptographic or data protection concerns

---

Overall Assessment: This is a straightforward wording change that improves consistency with naming patterns. The change is low-risk, but I recommend confirming that the shorter, more concise description won't cause confusion for administrators who need to understand what this policy controls.

[github-actions]

Checkmarx One – Scan Summary & Details – 867f59cc-bff6-4f98-88b2-2e7b2c432018

Great job! No new security vulnerabilities introduced in this pull request

[codecov]

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 51.86%. Comparing base (cfe818e) to head (d8ffbe7).
⚠️ Report is 12 commits behind head on main.

Files with missing lines	Patch %	Lines
src/Core/AdminConsole/Enums/PolicyType.cs	0.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6522   +/-   ##
=======================================
  Coverage   51.86%   51.86%           
=======================================
  Files        1902     1902           
  Lines       84058    84058           
  Branches     7501     7501           
=======================================
  Hits        43598    43598           
  Misses      38766    38766           
  Partials     1694     1694           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.