This module adds a configurable start screen so users can go right into their more common tasks.
It can be configured at the user level or just be used as common screens.
auto_awesome What this module does
AI-generated from the code · Odoo 20.0Lets administrators build configurable start screens made of action tiles (icons, images, descriptions) and assign one to each user, so people land on their most common tasks instead of a generic menu.
This module adds a personalisable "Start" screen: a grid of tiles, each one launching an existing Odoo action (a window, a report, a URL, a server action or a client action).
Where it appears in Odoo: - A new "Start" menu, visible only to members of the "Quick Start Screen" group, containing the start screen itself. - Two configuration menus: "Quick Start Screens" and "Quick Start Screen Actions". - On the user form, a "Menus Customization" section (visible to technical users) where a start screen can be linked to that user.
What users can do: - Create screens with a name and a list of actions, and open a screen directly from its list with a flash button. - Define each tile with a name, a rich description, an image or a Material Symbols icon name, a colour and a sequence for ordering. - Optionally add an extra filter (domain) and extra context to the launched action; these small expressions can use references to records and date helpers.
Automatic behaviours: - Tiles are shown in sequence order and inactive ones are hidden. - Only tiles whose target action the current user is allowed to read are displayed, so the screen adapts to each user's rights. - When a tile is clicked, its stored context and filter are merged into the launched action. - The screen opens as a tile board without the usual search bar.
Regular internal users can only read screens and tiles; full editing is reserved to administrators.
Depends on
Required by other modules
Menus it adds
Models and fields (3)
- res.users · extends an existing modelquick_start_screen_id
- quick.start.screen · new modelname, action_ids
- quick.start.screen.action · new modelname, color, image (Start screen icon), active, domain, context, sequence, icon_name, description, action_ref_id
Text generated by AI (DeepSeek) from reading the Odoo 20.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 4 confirmed, 5 with no information of 9 versions.
Sources · Odoo 20.0
Confirmed on 2026-11-03 in branch 20.0 of OCA/web.
terminal Installation and usage
OCA documentation · Odoo 20.0Configuration
Source · Odoo 20.0To create quick actions:
- Go to Settings > Technical > User Interface > Screen actions and create o modify an existing one.
- Choose the desired action, a name, a description and an icon.
- You can add an optional context so you can reuse existing actions. You can use
ref(<xml_id>)to get an id that you can use in your context. You can also usedatetimeandcontext_todayin that same way you can do inir.filters.
To create quick start screens:
- Go to Settings > Technical > User Interface > Quick start screens and create or modify an existing one.
- Choose a descriptive name and link some quick screen actions.
To assign a quick start screen to a user:
- Go to Settings > Users and Companies > Users and select one.
- In the Preferences tab, Menus customization section, you can choose which Quick start screen will that user use.
- If you want to make the user start always in their start screen, in the same section set the Home Action field to Quick Start Screen.
To activate the quick start screen menu for a user:
- Go to Settings > Users and Companies > Users (with debug mode on)
- In Extra Rights groups, set Quick Start Screen on.
Usage
Source · Odoo 20.0When you have the proper config, once you login, you'll go to the quick actions screen. Just click in and start working.
No verified information in OCA: Installation.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.