A Lovelace card that adds configurable restrictions (PIN, confirmation, block, hide) to other Home Assistant dashboard cards.
Restriction Card is a custom Lovelace card for Home Assistant that adds client-side security layers to other dashboard cards. It allows administrators to restrict access to specific cards using PIN codes, confirmation dialogs, blocking, or hiding based on user, conditions, or time. It solves the problem of controlling dashboard visibility and interactions in shared or multi-user Home Assistant environments.
Home Assistant users and administrators who need to control dashboard card access for different users, such as in family homes, shared spaces, or public displays where certain controls should be restricted.
Developers choose Restriction Card for its deep integration with Home Assistant's Lovelace UI, extensive customization options, and flexible restriction types without requiring server-side modifications. It's maintained as part of the HACS ecosystem and supports complex conditional logic and exemptions.
🔒 Apply restrictions to Lovelace cards
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports PIN codes, confirmation dialogs, blocking, and hiding with configurable options like retry limits and delays, as detailed in the restrictions options section.
Allows restrictions to activate based on entity states or attributes using comparison operators, enabling dynamic access controls tied to Home Assistant automations.
Offers theme variables and CSS overrides for lock icons, colors, and overlays, with examples provided for custom backgrounds and row styling in the README.
Permits specific users to bypass restrictions via user IDs, making it easy to grant admin or trusted user access without additional configuration, as shown in the exemptions options.
The README disclaimer explicitly states it's not for true protection, as restrictions can be bypassed by users with technical knowledge, limiting its use for sensitive systems.
Setting up multiple restrictions with nested options and exemptions requires verbose YAML, which can be error-prone and less intuitive than GUI-based tools.
Issues may arise where inner cards with high z-index are not fully blocked, requiring additional fixes with card-mod, as noted in the troubleshooting section.