DNN Forums

Ask questions about your website to get help learning DNN and help resolve issues.

Member Directory Module

Sort:
You are not authorized to post a reply.





New Around Here





    It seems that for a user to view the member directory, the only permission that works is if he is an administrator....

    I have a filter on the Directory that says only show memrbers of Group A.

    A user that logs in and is a member of group A see the message: "No members were found that satisfy the search conditions."

     

    If I make him an Administrator, he sees all memerbers of group A correctly.

     

    I dont understand...

     

    Thank you






    Senior Member





      The Users view was never meant to distribute permissions to view & manage users to anyone but the Administrators group.  That was always the case, since DNN was originally released. 

      If you want to have people only manage a subset of user accounts, you'll need to either (a) fork and change how an existing open-source user management solution works today, or (b) build a new one from scratch (or have a company build a new one that directly addresses your requirements).  

      Here is a list of our DNN extensions!






      New Around Here





        Will: Thank you - 

        Clarification, I am surprised when you say "The Users view was never meant to distribute permissions to view & manage users to anyone but the Administrators". This then means this is a module only for Administrators.  Is that correct?

        I hope not, because thats a really tight functionlity.

        To rephrase the question, if I have a series of DNN webpages with content specific for group A, then another set of pages for group B and so on,  and I want to display the members of Group A on that Group A page and Group B members for group B, you are saying thats not possible UNLESS the user is an administrator?  (I am not taqlking about management nor admin, only show the members of a specific group)

        Thank you for clarifying..

        Terry

         






        Senior Member





          Posted By ELC on 2/24/2024 7:46 AM

          Clarification, I am surprised when you say "The Users view was never meant to distribute permissions to view & manage users to anyone but the Administrators". This then means this is a module only for Administrators.  Is that correct?

          That is correct, but that's also why other alternative open-source and commercial extensions have popped up here and there over the years.  It's not the same use case for all website owners.  This is why some website owners assign so many Administrators.  In some cases, it's easier.  In other cases, they may not know that an alternative solution might be available.  

          Posted By ELC on 2/24/2024 7:46 AM

          To rephrase the question, if I have a series of DNN webpages with content specific for group A, then another set of pages for group B and so on,  and I want to display the members of Group A on that Group A page and Group B members for group B, you are saying thats not possible UNLESS the user is an administrator?  (I am not taqlking about management nor admin, only show the members of a specific group)

          I think it's great that you're re-phrasing, because I may have misunderstood the use case.  What I was saying is that it's not immediately possible for a user account to be able to manage a subset of the user accounts.  At least, not without implementing (a) way(s) to make this happen.  Also, I have a caveat to that, which I was thinking about when reading your response...  

          It would be possible to do that by creating what's known as "child sites" and ensuring that the respective groups of users are only assigned to the respective child sites.  From there, the main user account(s) that need to manage those users could be assigned as an Administrator of the child site.  This idea would require a proof-of-concept to prove it.  This is because the way cookies and permissions work, there may be side-effects in the UX that are not desired.  

          However, it actually sounds like you're looking to implement a granular set of permissions to display content differently to different groups of user accounts...  This is absolutely possible - and without any third-party tools or code!  

          1. First, you'd want to identify and name the different groups of users.  These labels will become the labels you should use for the names of Security Roles you'll want to create in the persona bar > Roles view.  
          2. Next, for the unique pages on the site that will be viewed by different groups of users, you'd want to uncheck the "All Users" and "Registered Users" in the view columns, and then only add the ability for the intended group(s) to access.  For example, Group A on some pages, Group B on some pages, etc.  
            1. From here, the modules (content) will follow the permissions set at the page level.  
          3. For pages where the modules might need to have different permissions for the different groups.  Say, a page is visible to different groups, but the modules on the page need to show/hide based on the group that is currently viewing the page. 
            1. In this case, edit the module settings for the respective modules.  
            2. Uncheck the checkbox that allows you to inherit the view permissions from the page.  
            3. Add the group(s) (security roles) to the permission grid, and be sure to check the View checkbox for those groups.  

          That's it!  This can be a bit time-consuming, but it's also a very powerful set of tools to accomplish what you're asking.  🙌🏽 






          New Around Here





            Will: gratitude!
            but I dont want to "What I was saying is that it's not immediately possible for a user account to be able to manage a subset of the user accounts" - the key word is manage - I dont want management, only viewing.

            Me, Terry, I am a member of club A. when I go the club A web page, since I am a member of the Club A, I want to see a list of all my friends who are also members of Club A. Towards that end, I will filter the Member Directory module to show only members of Club A.

            But, when I login and go to the Club A members page , I do not see all the Club A members (like I beleive I should) - remember, I am not talking about administrating the contents, only viewing the contents.... I see instead": "No members were found that satisfy the search conditions."

            Now, if I (Terry) become an Admin, I can see the list. So, I( cannot imagine a module like this that woould not let me, Terry, a member of Club A, see a list of all in that Club A group...it hurts to think about it... so I am thinking I have screwed up permissions somewhere (its always permissions :-) !!)

            Also, I am having difficulties finding membership module alternatives, so, if the above really does not work, a suggestion would be greatly appreciated. (sorry to bother you on a Sunday)
            T







            Veteran Member





              I am not an expert with the Member Directory module options, but I can say that we typically handle these types of business requirements using a structured content solution (in our case, 2sxc).  It is pretty straightforward to build an app that pulls DNN user profile information using a selected role (configurable per instance of the app).

              David Poindexter


              Creator:







              Senior Member





                Hello...  Thank you for clarifying what you're trying to do.  With this being the case, David's advice is what I'd also suggest.  You can use a structured content solution to list the user accounts as you're asking to do.  I know 2sxc has this, and also OpenContent has a User Management template that's already built in.  In your case, you'd just want to remove the editing/management features from the template.  Though, you'll probably have an easier time figuring out how to do it using 2sxc.  OpenContent has a much more techie UX.  

                You are not authorized to post a reply.

                These Forums are dedicated to the discussion of DNN Platform.

                For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

                1. If you have (suspected) security issues, please DO NOT post them in the forums but instead follow the official DNN security policy
                2. No Advertising. This includes the promotion of commercial and non-commercial products or services which are not directly related to DNN.
                3. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
                4. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
                5. No Flaming or Trolling.
                6. No Profanity, Racism, or Prejudice.
                7. Site Moderators have the final word on approving / removing a thread or post or comment.
                8. English language posting only, please.

                Would you like to help us?

                Awesome! Simply post in the forums using the link below and we'll get you started.

                Get Involved