A site I'm working on needs to allow for registered members (not back office users) to be given access to front end data/features if they are in a specific role and have been linked to the content they are viewing.
Whilst I can't go into specifics of the project assume we have an area called Restaurants and under that section are nodes Restaurant 1, Restaurant 2 and Restaurant 3. Let's also say we have permission levels of Restaurant Admin and Waiter. Restaurant Admin would provide full admin privilege against all restaurants and Waiter would provide cut down access
With Member Groups I can add a Member to both Restaurant Admin and Waiter but I can't figure out how to deal with the scenario where a member may be a Restaurant Admin against one particular restaurant but a Waiter against another. I don't even know if this is possible with Member Groups.
The solution I have come up with so far is to create a Document Type called Member Profile which can be created underneath each Restaurant node. In it is a property that links back to a Member and also a custom drop down containing the type of membership i.e. Restaurant Admin and Waiter.
This removes Member Groups from the equation altogether but feels clunky in that I am going to end up with a lot of repeated data in the Umbraco back office. The only other scenario I can think of is to provide Restaurant specific Role Groups e.g. Restaurant 1 Admin, Restaurant 2 Admin etc but this could mean the back office getting bogged down with Member Groups.
Linking Members to Roles to Nodes
Hi,
A site I'm working on needs to allow for registered members (not back office users) to be given access to front end data/features if they are in a specific role and have been linked to the content they are viewing.
Whilst I can't go into specifics of the project assume we have an area called Restaurants and under that section are nodes Restaurant 1, Restaurant 2 and Restaurant 3. Let's also say we have permission levels of Restaurant Admin and Waiter. Restaurant Admin would provide full admin privilege against all restaurants and Waiter would provide cut down access
With Member Groups I can add a Member to both Restaurant Admin and Waiter but I can't figure out how to deal with the scenario where a member may be a Restaurant Admin against one particular restaurant but a Waiter against another. I don't even know if this is possible with Member Groups.
The solution I have come up with so far is to create a Document Type called Member Profile which can be created underneath each Restaurant node. In it is a property that links back to a Member and also a custom drop down containing the type of membership i.e. Restaurant Admin and Waiter.
This removes Member Groups from the equation altogether but feels clunky in that I am going to end up with a lot of repeated data in the Umbraco back office. The only other scenario I can think of is to provide Restaurant specific Role Groups e.g. Restaurant 1 Admin, Restaurant 2 Admin etc but this could mean the back office getting bogged down with Member Groups.
Any ideas?
Hi Craig,
You can use relations types to relate content to members.
some references for you
https://our.umbraco.org/Documentation/Reference/Management/Services/RelationService
http://www.iceninemedia.com/articles/how-to-build-an-on-publish-event-handler-in-umbraco-7plus/
https://our.umbraco.org/projects/backoffice-extensions/nupickers/questionssuggestions/60250-How-does-relations-work
Hi Marcio,
Sorry for the delay in responding. That looks like a really good route for me to go down. Thanks for the advice!
Craig.
is working on a reply...