| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Project (project) |
| Lines of code | 367 |
| Technical Name |
psi_project_visibility |
| License | OPL-1 |
| Website | https://www.psilon.pl |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Project (project) |
| Lines of code | 367 |
| Technical Name |
psi_project_visibility |
| License | OPL-1 |
| Website | https://www.psilon.pl |
PROJECT VISIBILITY
THIS MODULE EXTENDS ODOO PROJECTS WITH ADVANCED VISIBILITY AND ACCESS RESTRICTIONS
SHORT OWERVIEW
This module modifies the default liberal behavior of the Projects module in Odoo, introducing enhanced control for project managers. It allows managers to restrict project visibility from general users, while simultaneously granting access to selected portal users. This feature enhances project security and data privacy, enabling targeted sharing of project information with stakeholders without compromising accessibility for authorized users.
THE MODULE WORKS WITH
odoo.sh
odoo community
ABOUT COMPANY
We have been active for more than 20 years in implementing ERP applications. Our core competencies in implementing Odoo ERP include the areas of warehouse management, production management and accounting. We are the authors of the link between Odoo and WAPRO Fakir software providing comprehensive support for Polish accounting. Check out our other applications at.
https://pomoc.psilon.pl/nasze-aplikacje
OUR SERVICES
Odoo Helpdesk
8:00/16:00 Monday - Friday (GMT+2)
Odoo Developer on Demand
Odoo Consultations & Learning
Odoo Implementations
SCREENSHOTS
PROJECT VISIBILITY
PROJECT --> PROJECT SETTINGS --> SETTINGS
Open the Projects app, choose a project, then navigate to its settings and locate the "Security" section.
Default Odoo behavior — internal users must be explicitly invited to access the project.
Default Odoo behavior — all internal users can see the project and its tasks by default.
Modified behavior — both portal and internal users must be invited to access the project. This serves as a secure starting point for further visibility customization.
Restores default Odoo behavior, allowing unrestricted access for internal users.
Reverts to Odoo’s default logic, which can be problematic — granting access to one follower may expose the project to all contacts linked to the same company.
A niche option — enables portal users to view archived tasks, if needed.
An additional safeguard — when disabled, portal users cannot be added as project followers, though they may still follow individual tasks.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. 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