When it comes to personalizing the post-login experience, there is one more way to tailor the information and tools users see on the page they land on. Instead of configuring visibility rules for individual blocks separately, you can group blocks together and manage their visibility conditions centrally. That’s where we’ll need the following tool. You can create new dashboards using configurable layouts, blocks, and widgets, such as recent content, announcements, shortcuts to common tasks, traffic statistics, notifications, and so on. Every detail in dashboards is highly customizable.
1. Redirect your Drupal users to relevant destinations
Redirect After Login
2. Create role-specific dashboards
Dashboard
3. Control block visibility under certain conditions
Block Visibility Groups
4. Custom event-driven post-login workflows
ECA (Event – Condition – Action)
Access to specific dashboards is controlled through this dashboard’s permissions.The Redirect After Login module provides a simple interface where you can specify where users with different roles start their post-login journey.
Final thoughts
The ECA (Event – Condition – Action) module lets you create configurable workflows of any complexity using a visual builder, with no need to write custom code. You define the event that triggers a workflow, the conditions that must be met, and the actions Drupal should perform. Here is an example for post-login personalization:Each dashboard can serve a specific audience or workflow. For example, you can create a dedicated dashboard for event coordinators and use the dashboard’s permissions to make it available only to this role.Redirects, tailored dashboards, and block visibility rules can improve the post-login experience on their own. But when you need to combine multiple triggers, checks, and responses into a single fluid workflow, this is where Drupal’s ECA (Event – Condition – Action) module truly shines.
