Skip to main content
Drupal is a registered trademark of Dries Buytaert
Release: OpenID Connect / OAuth client 3.0.0-alpha9 New alpha version released for module openid_connect (3.0.0-alpha9). Release: Timelinr 1.0.1 Minor update available for module timelinr (1.0.1). Usage Milestone: Simplify Module simplify crossed 10,000 active installs. Usage Milestone: Views Reference Filter Module entityreference_filter crossed 10,000 active installs. Usage Milestone: Dropdown Language Module dropdown_language crossed 10,000 active installs. Usage Milestone: Paragraphs Browser Module paragraphs_browser crossed 10,000 active installs. Usage Milestone: OpenAPI Module openapi crossed 10,000 active installs. Usage Milestone: Decoupled Router Module decoupled_router crossed 10,000 active installs. Usage Milestone: Time Field for Drupal 8+ Module time_field crossed 10,000 active installs. Module Revived: Entityqueue Buttons 1.1.2 Module entityqueue_buttons updated after 8 months of inactivity (1.1.2).

Site Assistant

Security covered Drupal 10–11
View on drupal.org

Site Assistant allows you to create helpful guides that appear on your website to assist users. You can define specific conditions for when these guides should show, and fill them with various types of content or link to library items for reuse. This is useful for providing targeted help, like a journalist-specific guide or different support for logged-in versus anonymous customers.

Overview

With Site Assistant you can create assistants that can help your users navigate better, faster and more targeted on your website.

Assistants basically consist of two fields. One is the content field where you can place an unlimited amount of assistant list entries. And the other field "Visibility conditions" is where you configure the conditions when the assistant should be used. (See: Condition plugin system)

Assistant list entries are content entities that come in different shape and functions. They vary from very simple "Headline" to more complex "Subpage". You can even define your own assistant list entry type.

Assistant library items are content entities that are design to be reused over multiple assistants. They basically are a collection of assistant list entries.

Use cases

Example 1 - Public relations

You have an area on your website that is dedicated to journalists. All content in this area is located under http://example.com/public-relations.
So you create an assistant that is targeting journalists by using a path condition public-relations/*.
The assistant is filled with useful information for your target group, like "how to get accredited" or "access to our pr material" or "contact our pr manager".

Example 2 - Customer

You run an online shop and want to support your customers based on their needs.
Customers that are not logged in yet should see an assistant that helps them find the products they need and customers that are logged in should see an assistant that helps them with their existing order.
So you create two assistants, number on is targeting anonymous users to you use the user role condition and set it to anonymous. The other assistant is targeting logged in users so you use the user role condition set to role "customer".
Each assistant can have its own content, but for shared content, like general information, you can use the assistant library item and share the content across both assistants.

Dependencies

Blog posts

Depends on

Dependencies of the latest stable release

Required by

Tracked projects that depend on this one

No tracked projects depend on this one yet.

Activity

Tracked releases
5
Tracked since
Dec 2025
Latest release
1 month ago
Releases (12 mo)
5 ▲ from 0
Maintenance
Active

Release Timeline

Releases

Version Type Core Release date
3.0.0-alpha1 Pre-release 11 Jul 3, 2026
2.0.0 Stable 10–11 Jul 2, 2026
3.0.x-dev Dev 11 Jun 26, 2026
2.0.x-dev Dev 10–11 Dec 4, 2025
2.0.0-alpha1 Pre-release 10–11 Dec 4, 2025