Hello
I don't know what is the right component for my issue. It is about visibility to have an add-on write permission as follow:
I have been able to pretty much set up oa to work for my need and this is the last part and I need help.

Before I decide to use oa, I was using nodeaccess_nodereference and nodeaccess_userreference to not only control visibility but also in its setting I was able to set which content type these referenced users/nodes were able to create. In essence it served dual purpose.
I know that in each section we can set up read permission or visibility, but I have an additional section called project section that I need to be able to allow the groups chosen the ability to write a certain content type for the project section they were chosen.

I need it simple for obvious reason that clients are from all walks of life, and this needs to be simple.

Basically I have created blueprints for client space and groups space. in client space they are only allowed to create project section. Now I need to be able to give them the autonomy to select which groups can see their project but at the same time to give that group permission to create a proposal content type in this section so client can decide which group to choose.

Can I use the nodeaccess_nodereference and nodeaccess_userreference for visibility only on this section?? This way I can give read and write a certain content type permission.

Or will it interfere with something I cannot see???

Comments

hefox’s picture

My suggestion is try to find a way to to implement it without adding any additional access control modules.

I'm not totally sure your setup, it seems like you got some costume content types. The term 'groups' is used in various ways in og/openatrium, but sounds like you've had a type of space called groups? My suggestion is to be bit more verbose with your exact current setup.

sophiejones’s picture

Hello
The site is set up for set of professionals in field of art, design, engineering. they are set out globally and work in groups.

Top echelon spaces are created by site administration and are based on categories in art, design and engineering. These professionals create their group and members. They are then allowed to create a space from which they can do their work. Their group is among parent of this space. I used blueprint to create different type of spaces and permission to make it easier and it works.

The registration system in the site, has a process that makes it easy to find out which new users are client, they are then given the site role designed for clients and are automatically member of a administrative space called client area. In this space they are allowed to create project section which has two content type: project, proposal
These clients are allowed to create project section and project content type where they outline their project and its parameters.
We run some test and it seems 82% of our test-clients are interested to keep project private and choose who can propose and they actually loved the idea and the flow that allowed them this easily.

They can choose to keep this private or public. If public, it goes to a view we call project wall. Then all the groups can see it and if they choose, they can create proposal and submit it. If project is kept private, then there are group walls view where clients can go and view groups (actually it is their spaces that show here) We have a custom view plugin that creates these walls where for users convenient is capable of allowing them to view details of each grid right in the view page without being redirected. Then using flag module, client can select the groups. and then bulk assign them to their project. All of these works nicely after some customization using openatrium permissions.

I now have a problem. I need to find a way to allow these groups to create proposal content type on these project sections and I have no idea how to do that in a practical manner. My problem is that client area is not about user membership, is about content only. If I can figure out how to manage this part, I have already figured out the rest of the flow nicely. Just this particular part escapes me.

I hope this clarifies it.