I am currently using Drupal's Project module to run a client/developer interface for my web design company. I would like for a client to only see their project and the issues for their project, while not having view access to any other project/issue. They may not be the creator of the project or issue, so 'access own project' permissions would have limited success. I have a hard time believing that I am the first person to ask for this type of access control, but the issue queue seems to indicate otherwise.

I know that with OG and the OG_Project module, it separates projects into their own OG, but I cannot seem to disallow view permissions for projects and issues based only on group. From an issue that I've posted in the OG_Project module's issue queue, it can't really be done with OG at all. This is a serious problem, as I have clients who are waiting to log issues until they are comfortable that there will be no potential disclosure. Has anyone else done this on their site?

Comments

aclight’s picture

aclight commented
Priority: Critical » Normal

This is not critical.

mlncn’s picture

mlncn commented
Version: 5.x-1.1 » 5.x-1.3
Status: Active » Closed (fixed)

We're using organic groups with project module, and if the group is marked as private, and the posts (issues) are left as private, the access control works fine: people only have access to groups (which are also project-project nodes for us) for which they are members.

benjamin, Agaric Design Collective