Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By acostanza on
I want to be able to give users the ability to decide if a node they create is available to others to view. The idea is to have a place where a registered user could work on a node and save it, keep it private (unpublished) and then publish it when they wanted to.
I would use this functionality for projects that are sensitive until they are done. Ideally, the author of the node, or their group of nodes, could choose to let others in his/her team view it, or make it available to the rest of the public.
Is there any way to do this in Drupal? I can't even figure out how to give the user access to even toggle published/not published for their node without giving them full node administration.
Any thoughts would be greatly appreciated!
-Adam
Comments
check out the
check out the workplace.module
--
www.bargainspy.co.uk
--
Ixis (UK): Drupal support, Drupal hosting.
This is one area where
This is one area where drupal is not terribly strong sadly.
Honestly, the simple answer to your question is, well, there's no simple answer.
With available modules for access control, you'd have to do this by roles. What you could do is create a role for each person/group that needs this functionality and then install one of the modules, simple access probably would work best, which would allow them to restrict access to just that role.
This actually works fine, except that your role admin page can get unusuable quickly if you have a large number of roles. Sadly, drupal does not provide any method to restrict access to users instead of just roles, a functionality I think would be really handy.
Oh, and to allow toggling the published/not published role, you have to grant the user full node administration. Another thing I think could be improved on...
I've not used it myself, but
I've not used it myself, but maybe the workflow.module and actions.module may help the publishing of nodes with out the need for full node administration permissions.
--
www.bargainspy.co.uk
--
Ixis (UK): Drupal support, Drupal hosting.
Other possible options
I don't know any of these modules very well, but it's possible that these might be of some help:
Organic Groups
http://drupal.org/project/og
E-Publish
http://drupal.org/project/epublish
Good luck.
Simple Access and workspace module
If Simple Access and workspace module worked together, I think I'd have a working solution for what you've descriibed. The nodeperm_role module was supposed to work with workspace, but nodes get replicated many times in workspace, making the workspace module pretty much unuseable with access to nodes (unless the user actually creates the node-- then this is a different matter). I need, however, to be able to assign editing/authoring permissions of certain nodes to certain users, so I'm waiting for an update to workspace.module.