Adaptive Activity Management ⸱ Activity Studio One
by Sveltware Solutions https://www.linkedin.com/in/sveltware$ 168.00
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Community Apps Dependencies | Show |
| Lines of code | 1441 |
| Technical Name |
svn_activity_hub |
| License | See License tab |
| Website | https://www.linkedin.com/in/sveltware |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Community Apps Dependencies | Show |
| Lines of code | 1441 |
| Technical Name |
svn_activity_hub |
| License | See License tab |
| Website | https://www.linkedin.com/in/sveltware |
A dedicated workspace for activities in Odoo. Designed to bring clarity to follow ups without forcing new workflows. Built on Odoo's native activity system for long term use.
Activity Hub
Activities are collected in one place. Users triage, process, and organize work with clear intent and structure.
Daily Execution
Activities are handled as a work queue. Priorities, deadlines, and bulk actions support continuous execution.
Ownership First
Ownership boundaries are respected by design. Collaboration is supported without compromising control.
# Activities are treated as signals, not as work
In Odoo 18, activities work as short lived signals attached to records. They surface at the right time to support follow ups, then disappear once the action is completed. Activities function as prompts on records rather than independent work items with their own lifecycle.
- Completed activities are removed by default in Odoo 18, so activities do not retain their own lifecycle.
- Done feedback is posted on the record, so the activity itself does not retain its outcome as a first class object.
- Activities appear on records, in activity views, and in the tray near the user avatar, but there is no dedicated activity hub.
- Activities do not provide priority, reminder, participants, or tags, so they remain lightweight and record centric.
- Visibility is broad by default, and there is no optional governance mode to scope activity access.
Activity Studio starts from a different assumption. In many organizations, activities are not just signals. They are work.
It keeps the native activity system intact, then extends it into a dedicated workspace. Activities can be processed daily, reviewed after completion, and organized with clearer responsibility and structure.
Odoo treats activities as signals. Activity Studio treats them as work.
# Users think in attention states, not in records
In Odoo 18, activities and chatter are primarily accessed through records. This model is consistent for data and history. In daily work, however, users do not begin by opening records. They begin by deciding what requires attention. These decisions are simple and repeat every day. What is overdue. What needs attention today. What is planned. What involves me. These are not domain questions. They describe attention states.
When information is presented mainly as a record stream, attention becomes fragmented. Important updates mix with secondary context. Decisions made earlier are harder to locate. Users read more and scan less.
Activity Studio organizes activities around attention states. Work is grouped by time and scope rather than record location. Completed work remains reviewable. Activity related messages become readable in day to day follow up.
Users do not work record by record. They work by managing attention.
# Clear ownership with safe collaboration
Activity Studio clarifies responsibility without restricting collaboration. Owner, creator, and participant are treated as separate roles. Shared users can follow progress and receive reminders. Editing and deletion rights remain restricted when a user is not the owner or creator.
Governance is optional. My Activities Only limits activity visibility to items the user owns or is shared on. All other activity behavior remains unchanged from Odoo core.
Collaboration works without weakening ownership.
# History is only useful when it can be reviewed
In Odoo 18, activity related messages are mixed into record chatter. This preserves a complete history, but makes review difficult during daily work. Users often know what they are looking for, but not where to find it.
During execution, users need to quickly answer practical questions. What feedback was given. Who was involved. What was decided. A continuous message stream does not support this kind of review.
Reading the entire chatter thread is rarely practical. Important decisions are buried among notifications, status changes, and unrelated updates. History exists, but attention is fragmented.
Activity Studio introduces smart chatter filtering. Messages can be reviewed by type, timeline, and recipients. Users scan decisions instead of reading entire threads. History becomes usable during real work.
History only helps when it supports decisions.
# Demo, installation, and dependencies
Activity Studio One is built as a backend extension for Odoo 18. It integrates directly with the native activity system and does not introduce a parallel workflow. The module can be evaluated safely on a demo database before deployment. No data migration or destructive changes are required.
Demonstration
A live demo environment is provided to showcase the activity workspace, attention based triage, ownership boundaries, and smart chatter filtering. The demo reflects a realistic Odoo setup rather than a scripted scenario.
Installation
Installation follows the standard Odoo module process. Once installed, the Activity menu becomes available. Access is controlled through dedicated activity user groups and does not alter existing access rules.
Dependencies
Activity Studio One depends only on standard Odoo backend modules. No third party services or external libraries are required. Compatibility is maintained with common Odoo customizations.
Configuration
Default behavior is designed to work out of the box. Optional features such as governance mode, reminders, and visibility scopes can be enabled selectively without changing user workflows.
Experience real-world usage at production level. Just visit the link to explore in action.
Sveltware Proprietary License v1.3 Copyright © 2025 Sveltware Solutions All rights reserved. ------------------------------------------------------------------------ 1. Grant of Use Subject to the terms of this License and payment of the applicable fees, the Authors grant the Licensee a non-exclusive, non-transferable, perpetual license to install and use the Software for one (1) production purpose. A production purpose means the operation of the Software for a single customer or a single production environment. - Each additional customer, project, or production environment requires the purchase of an additional license. - Use of the Software for development, testing, or evaluation that does not generate revenue is permitted without additional licenses, provided that the Software is not distributed or made available to third parties. 2. Distribution and Resale The Licensee may not publish, distribute, sublicense, rent, lease, sell, or otherwise provide the Software (in original or modified form) to any third party, except under a separate written agreement with the Authors. Developing Odoo modules that depend on the Software as a library (e.g. importing or extending it) is permitted, provided that no source code of the Software itself is copied. Such modules may be distributed under any license that is compatible with this License (including LGPL, MIT, or proprietary licenses similar to this one). 3. SaaS and Multi-Tenant Use Operating the Software as part of a hosted service or SaaS offering that serves multiple third-party customers is considered a form of distribution. This is not permitted under this License. To use the Software in a SaaS context, or to make it available to multiple third-party customers, the Licensee must obtain a separate commercial agreement with the Authors. 4. Modifications The Licensee may modify the Software for its licensed purpose. Modified versions are subject to the same restrictions as the original Software and may not be distributed without written authorization from the Authors. 5. No Warranty THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module