Skip to content

[19.0][FIX] dms: count users who get an access group's Odoo groups by implication - #537

Open
nachdjo wants to merge 1 commit into
OCA:19.0from
novoauxilia:19.0-fix-dms-access-group-implied-users
Open

nachdjo wants to merge 1 commit into
OCA:19.0from
novoauxilia:19.0-fix-dms-access-group-implied-users

Conversation

@nachdjo

@nachdjo nachdjo commented Oct 30, 2026

Copy link
Copy Markdown

In 19.0, res.groups.user_ids only has users put in a group directly. Users who get it through another group (DMS managers get DMS user that way) are only in all_user_ids. So an access group built from Odoo groups leaves them out and they can't see its directories.

  • _compute_users uses group_ids.all_user_ids
  • post-migration recomputes existing access groups (19.0.1.1.7)
  • 3 tests: implied users are members, a user given an implying group later joins, a manager finds a directory shared with DMS users

We hit this on a production database after moving to 19.0.

🤖 Generated with Claude Code

…cation

Since 19.0, res.groups.user_ids only holds the users explicitly in a group;
users who get it through another group (e.g. DMS managers, who imply DMS
users) are only in all_user_ids. An access group built from Odoo groups
therefore left those users out, and they lost access to its directories.

Use all_user_ids, and recompute existing access groups on upgrade.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@oca-cla-bot

oca-cla-bot Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

All commit authors signed the Contributor License Agreement.

CLA signed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants