dotCMS / dotCMS/core

Get roles attached to a folder by the folder identifier or inode

Open
#33,076 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

OKR : Customer Support Team : Maintenance Type : New Functionality
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

User Story

Currently, there is no direct way via the Roles or Permissions APIs to retrieve which roles are assigned to a specific folder (by ID or inode).
Our end goal is to determine which users have access to a given folder, and while we can already get users by role (/api/v1/roles/{roleId}/rolehierarchyanduserroles), the missing piece is the ability to query roles assigned to a folder.

The expectation is that we should be able to start from a folder ID (inode) and trace:
Folder → Roles → Users

So if you had a folder identifier or inode (example: id some-random-folder-id) using the roles api, can you see what roles are attached by filtering by that ID?
Our end goal is that by using the roles or users API, We should be able to get what users have permissions to a given folder given you have the a folder ID or inode.

Acceptance Criteria

Roles or Users api must expose an endpoint to fetch all the users or roles assigned on a particular folder.

Proposed Objective

Customer Support

Proposed Priority

Priority 3 - Average

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

https://dotcms.freshdesk.com/a/tickets/32589

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing Roles and Permissions APIs, especially /api/v1/roles/{roleId}/rolehierarchyanduserroles, and trace how folder IDs or inodes are represented. Define the endpoint needed to retrieve roles or users for a folder, then verify that the API supports the documented Folder → Roles → Users flow and meets the acceptance criterion.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
authorization, backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.