Posted by guerinteedmike on January 12, 2016 at 5:27pm
I have a request to allow access and notifications to be sent to a single piece of content - a private message for example. I am wondering if permissions can be set at the node level in OA.
Scenario - A project space contains a messaging section that is used for communication between internal team and clients. The messaging section will be set up to allow access via a team and notifications will go out to the whole team. Is it possible to configure a single message (discussion node) to only to be visible and send notifications to a single member of the team?
regards,
mikeg
Comments
Private messaging
As far as I know this is not possible in OA, as access is given by the setup of the section. You would have to create a section where only the two people who communicate privately would have access to.
A better alternative is probably to setup the privatemsg module. I have set it up myself on an OA instance and worked ok. I unfortunately had no time to do a proper development into a feature, but I believe that would be a plus to have for the OA distribution and would be happy to cooperate with efforts on that direction.
It is possible to subscribe
It is possible to subscribe to a single node. This should be done by the logged in user. Then when the node is updated a message will be sent to the subscribed user(s).
Solution - Private messing in OA
For the benefit of those who may be looking for something similar...
1 - subscribing to a post will create messaging for only those who subscribe but does not limit access
2 - The OA solution is to create a new discussion section (or content type of your choosing) and add only the users that need to see/receive notification. This will create a private area for messaging.
another alternative was recommended by gianhiano above which requires extending OA - "A better alternative is probably to setup the privatemsg module. I have set it up myself on an OA instance and worked ok. I unfortunately had no time to do a proper development into a feature, but I believe that would be a plus to have for the OA distribution and would be happy to cooperate with efforts on that direction."
@ solution 1: I'm not sure
@ solution 1: I'm not sure what you mean by "does not limit access". Eg if a document is in an OA section with limited access only those who are granted access will be able to subscribe to it, and thus only they will see any updates.
Response -> @ solution 1
correct. A sections defines visibility for itself and its assets. A single asset cannot have it's own permissions.
So you cannot have a section that has assets for a group of people and create a single document in that section that will only be visible and set notifications for only a specific user. To do this in OA you would need to create a new section as described in @2 above.
So you cannot have a section
That is the correct way to do it in open atrium, or so i believe.
But since OA is based on organic groups and sub-groups, it should be possible to transform the asset in a group and then give it a single member. I don't really recommend this solution, i cannot really predict the consequences (with the notification system and others) with the rest of OA functionalities.
Idea?
Mmm perhaps an experiment with adding the Group and Section field to a content type. That would make each single node Group and Section aware.