Improve login UI transparency for persistent sessions

[sahillllllllll-bit]

Summary

Rocket.Chat maintains persistent sessions on the same system by default. However, this behavior is not currently communicated on the login screen.

Problem

Users may reasonably expect to be logged out when closing the browser. The absence of any indication on the login UI can lead to confusion or incorrect assumptions about session behavior.

Proposed Enhancement

Add a small, UI-only indicator on the login screen (for example, helper text or an informational element) to clarify that Rocket.Chat already maintains persistent sessions on the same system.

This would be purely informational and would not change any authentication or session logic.

Scope

• UI/UX only
• No backend or security behavior changes

Additional Context

I have a UI-only implementation ready and can open a PR if this approach aligns with project direction.

Login Page Before

Login Page after

Signup page After changes

Feedback and suggestions are welcome.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Related PRs

#36888 - test: flaky should reset e2e password from the modal [merged]
#36947 - test: Add waitForLogout in logout action [merged]
#37345 - fix: Administration settings not being listed after logout and login [merged]
#37845 - fix: prevent push notifications from being sent after logout [merged]
#37846 - fix: update /v1/users.logout to properly log out all user sessions [merged]

👤 Suggested Assignees

• dougfabris
• ricardogarim
• aleksandernsilva

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[Rahulyadavv123]

Hey Everyone , I am new to open source and i'd like to start with small frontend contribution and , I’d like to work on this. Could you please assign this to me?
@sahillllllllll-bit @dougfabris
@ricardogarim @aleksandernsilva @reetp

[sahillllllllll-bit]

Hi @Rahulyadavv123,
I’m also new to open source, and this is my first contribution. I’ve already created a PR for this issue and am currently waiting for a review from the maintainers.

A couple of tips from my experience so far:

Please read all the contribution guidelines before getting started.
Avoid mentioning people randomly, as that can lead to moderation issues.
If you need any help, feel free to reach out.

[reetp]

Hey Everyone , I am new to open source

In which case read before you write. Lots. This is an issue tracker, not a help forum.

Dev guide

Ask for help in the appropriate place.

Also read the Github section carefully.

reetp

Do not @ people you do not know, do not know if they work here, or are the right person, in the hope you'll get some attention.

You will muted or blocked.

[Rahulyadavv123]

Hey Everyone , I am new to open source

In which case read before you write. Lots. This is an issue tracker, not a help forum.

Dev guide

Ask for help in the appropriate place.

Also read the Github section carefully.

reetp

Do not @ people you do not know, do not know if they work here, or are the right person, in the hope you'll get some attention.

You will muted or blocked.

Sorry Sir. I will never do this mistake again..

[AbhijeetShk]

Is this issue still open and need contribution?

[reetp]

Is this issue still open and need contribution?

Before wasting your time see notes above about how to check if they want a "fix".