[18.0][ADD] base_group_subcontractor: Extra user type group for restricted access to backend#966
Open
pedrobaeza wants to merge 1 commit into
Open
Conversation
…access to backend TT63310
OCA-git-bot
added
series:18.0
mod:base_group_subcontractor
christian-ramos-tecnativa
approved these changes
Jul 1, 2026
christian-ramos-tecnativa
left a comment
christian-ramos-tecnativa
left a comment
There was a problem hiding this comment.
Functional and code review OK!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This module adds a new isolated user type group called "Subcontractors", that simulates to be an internal user, giving access to the backend, but only granting the minimum permissions for the web client to work, and only exposing the Discuss menu.
The rest of the needed permissions for that subcontractors should be given in extra customizations.
Use Cases / Context
A usual need inside a company using Odoo is to have external people (subcontractors) that need to access Odoo to do certain operations that are not allowed (or they are not comfortable) in the portal, but giving them an internal system user is too much, as there some visible information (like contacts or calendar events) that shouldn't be shown by these users, even by legal reasons (GDPR, etc).
Known issues / Roadmap
@Tecnativa TT63310