Even though the module works as described, I am just now considering how it might be used.

I am wondering if it would be possible to limit the options available to the author/editor of the node to only those roles they themselves have out of those that the OG configuration permits. e.g. if the author is only an authenticated user they can permit all authenticated users to see the post in addition to those in the group, whereas if they are also an editor they could have the choice of making it visible to editors or authenticated users.

As I said earlier I am just coming to grips with the uses of this module and I hope this suggestion is not premature.

Thanks,

Izzy

Comments

izmeez’s picture

izmeez commented

You know what they say, "Be careful what you ask for, you may get it."

I am not even convinced that this is a feature I would want if it were a permanent restriction.

I would like to hear what other people think about the various use cases for this module and the features that would be best.

Thanks,

Izzy

marcp’s picture

marcp commented

This is an interesting idea but one that probably wouldn't make it into the module. It wouldn't be hard, though, to write a separate module that was weighted higher that would alter things to make it work.

I'll leave this active for a while to see if anyone else cares to chime in.

ldekay’s picture

ldekay commented

I'm not sure why this option would be desirable, BUT I would like to be able to PREVENT anyone NOT in the posting group from viewing the content node. It appears that currently any users who have the authorized role(s) have access to the content. There should at least be an OPTION to allow only members of the selected group(s) with authorized role(s) to be able to access restricted content.

This is needed to restrict viewing of sensitive documents to ONLY a select group of user roles within the target group. For instance, we might want to restrict access to sensitive financial data to the Officers role of the Finance Team, the Management Team and the Board. Or, sensitive Negotiation documents might need to be restricted to the Negotiator and Officer roles of the Legal and Management Teams.

I currently have a similar situation with postings on the website of a club with several different chapters. Officers of the chapters have sensitive board documents and information they aren't ready to share with their chapter members or with ANYONE in the other chapters. Does anyone have a workaround to do this?

As it is, I have to ask, "Where's the OG in OG Access Roles?" I'm afraid I can't see the point of an OG module granting access to authorized roles regardless of the group they belong to. It seems like this is overriding the whole point of Organic Groups. Can anyone explain the logic behind this?

bonobo’s picture

bonobo commented
Status: Active » Postponed

Setting to postponed, as this hasn't developed much traction.

As marcp said, the way to do this would be through a helper module that delivered this functionality -

One concern on this: let's say that, in an academic setting, a teacher wanted to post something that was visible to parents and students, but not other auth users. If the use case described in this ticket was executed, a "teacher" would need to be in the "student" and "parent" role in order to post content that would be visible to them.

From a technical place, this is manageable, but from the perspective of using roles to accurately describe what a person does, this would not work well.