[I] Feature Request: Access Control for Viewing Articles [answer]

["riirxx (via GitHub)" <gi...@apache.org>]

riirxx opened a new issue, #1264:
URL: https://github.com/apache/answer/issues/1264

   ## Is your feature request related to a problem? Please describe
   
   Currently, all users can browse all articles without any access restrictions. However, in some cases, we need to limit access so that only specific user groups can view certain articles.
   
   ## Describe the solution you'd like
   
   I would like to request a permission-based access control system for browsing articles. Specifically:
   
   Each article should have an associated access group.
   Only users belonging to the assigned group should be able to view the article.
   Unauthorized users should receive a "Permission Denied" message or be redirected to a different page.
   
   ## Describe alternatives you've considered
   
   A few potential solutions could be:
   
   Role-based access control (RBAC): Define roles (e.g., admin, editor, viewer) and associate them with article access.
   Group-based permissions: Users can belong to different groups, and articles can be restricted to specific groups.
   Tag-based restrictions: Articles could be tagged with access control levels (e.g., "internal only", "public").
   
   ## Additional context
   This feature would enhance security and provide more control over sensitive or internal articles.
   It would be helpful if there were an admin panel where permissions could be managed easily.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@answer.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Feature Request: Access Control for Viewing Articles [answer]

["HayHiTee (via GitHub)" <gi...@apache.org>]

HayHiTee commented on issue #1264:
URL: https://github.com/apache/answer/issues/1264#issuecomment-2690306382

   Yeah I totally agree with you. I think Group-based permissions is the best to go as you can group contents and users. You can also have sub-permission in group-based permission using role-based access control ((e.g., admin, editor, viewer)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@answer.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Feature Request: Access Control for Viewing Articles [answer]

["hepisec (via GitHub)" <gi...@apache.org>]

hepisec commented on issue #1264:
URL: https://github.com/apache/answer/issues/1264#issuecomment-3000587550

   If you consider existing installations, I'd suggest the following approach:
   
   - add an administration option to enable groups, let's call it `groups_enabled`
   - when a new question is created and `groups_enabled` is `true`, the user **can** select one or more groups the question will be assigned to, but this is optional
     - the user can only assign groups he is a member of
   - when a question is not assigned to a group, it is considered "public" (= visible for all users), this is the default for all existing questions in an existing installation after this feature becomes available
   -  when a question is assigned to one or more groups, only members of the assigned groups can see the question (and answers, of course)
   - the administrator can manage groups and group members
   
   Additional feature:
   
   - a user can subscribe to questions in his groups the same way he can subscribe to questions of specific tags 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@answer.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@answer.apache.org
For additional commands, e-mail: issues-help@answer.apache.org