Expose the Currently Logged-In User (current_users) in Lovelace and Templates and more

[penguin-fr]

📋 Summary

Currently, Home Assistant does not natively expose which user is viewing or interacting with the Lovelace interface, making it difficult to personalize the UI or automations based on the logged-in user.

We propose introducing a current_user context (or equivalent) that can be accessed in:

• Lovelace cards,
• Jinja templates,
• and automations,

to dynamically adapt the smart home experience per user.

🎯 Goal of This Feature

Home Assistant allows multiple users with different permission levels. However:

❌ There’s no way to dynamically access the currently logged-in user in Lovelace or templates;
❌ Multiple users interacting at the same time (e.g., on different phones) cannot be handled cleanly;
❌ There is no direct link between user, device_tracker, and person in templates.

✅ What We’re Proposing

1. Expose the current user (current_user) in Lovelace, templates, and automations
2. Support multiple simultaneous active users, each with their own context
3. Allow conditional customization based on the current user

🔧 Implementation Ideas

Expose a structured current_user object, e.g.:

{{ current_user.id }}
{{ current_user.name }}
{{ current_user.is_admin }}
{{ current_user.device_trackers }}
{{ current_user.person_entity }}

Make this object available in:

• Jinja templates (for sensors, automations, scripts…);
• Dynamic Lovelace cards (like config-template-card, conditional, etc.);
• User-specific tap_actions;
• Optionally in blueprints.

🧪 Real-World Use Cases

🔐 Security & Restrictions

• Show a "Open Gate" button only if the user is allowed and near home (using proximity);
• Hide switches or alarm controls from kids, but display them to parents;
• Require a user-specific PIN for sensitive actions.

📍 Presence

• Detect the actual user interacting with the UI, not just who is physically at home;
• Enable personalized automations: e.g., set different comfort temperatures, lighting scenes, or media based on who is using the interface.

💡 Feature Suggestion

Expose a native API or variables like:

current_user # object or dictionary
current_users # list of active users

Make them accessible in:

• Templates (state, automation, script, etc.);
• Lovelace frontend;
• Optionally in events (user_logged_in, tap_action, etc.).

🙏 Thank You

Several members of the French-speaking Home Assistant community have explored every available workaround.
This feature would unlock true multi-user, secure, and dynamic personalization, making Home Assistant even more powerful.

[penguin-fr]

So it needs some development to make that happen

[penguin-fr]

If my post is not clear enough i'll try it in a different way:
On one dashboard, if the user logged validate his position regarding a specific zone, then a button is visible, if the user logged is not in the specific zone, then button is not visible. If you have several users logged at the same time, then the button must be visible or not visible for each user logged.
Today I copy/past the same dashboard and I allow one user per dashboard. This is the only way I found to fit my needs.

[karwosts]

I agree this doesn't really make sense. There is only one template usage in the frontend cards (markdown), and that supports the user variable.

So what else is it missing from? Are you asking about custom cards, or are you really asking to support templates in more places?

[penguin-fr]

Ok, so it looks like I didn't express myself well.
I'll give you my example : This is a piece of my code :
cards:
- type: conditional
conditions:
- entity: person.name
state:
- home
- zone1
card:
type: button
name: Gate
icon: mdi:gate

How to change that code to ensure that for 10 users, My card is visible for EACH user only if they are in "home" zone or in "zone1" zone ?
Today I don't know how to do, so I copy / past my dashboard 10 times to check the location and visibility for every single user.

[karwosts]

So sounds like what you're asking for is either a template condition, or a "current user in zone" condition.

[penguin-fr]

Perhaps I can deal with my needs with a script.
But I'm a beginner in HA and i'm not a developper.
I just like HA and what we can do.
I'm just never enough

[karwosts]

Pending PR #26401 may (at least partially) provide what you're asking for.

[penguin-fr]

Looks like yes ! 😄
Question is : Does it work with several users logged at the same time ?
(check association between user logged and user location for every single user connected)

[karwosts]

Question is : Does it work with several users logged at the same time ?

Yeah, all the logic there runs in the frontend, so it's just aware of the current logged in user, and it should scale to any number of separate clients running simultaneously.

[penguin-fr]

Wonderful, thanks for putting this evolution to life ! 😄

[oerix]

#26401

Does this expose syntax to be used with templates? As far as I can see the PR is mainly UI based option.