Background
I wish the editbar action to only be enabled for some users; other usernames
should
not be able to edit paragraphs.

Research
In http://osdir.com/ml/cms.magnolia.user/2006-12/msg00045.html Sameer
Charles states:
You can always assign permissions on paragraphs or even properties.

its the GUI which does not allow browsing that deep, try to add ACL like
"read only" -- "selected and sub nodes" -- "/home/newsParas"

And the 3.x documentation states:
"The visible property is not on a per-user base. If you want certain users
to not see certain templates you can define a new Role in Security and deny
the access to the Template Definition content node."
---------------------------------------------------------------------------
I created a role (deny access) and applied it to 
(config repository) /modules/templating/paragraphs/mypagraph,
and associated it with a username/password (and group).  But I can edit the
content when signing in with the  username.   I do not see the content
repository listed in the roles dialog ... I
just see Website, Users, Config, Roles, Store, Expressions, Documents, and
Groups.
I browsed the content repository with the Tools | JCR browser, seeing the
content, but I don't
see how security can be associated with any of its nodes.

My interpetation is that security is being applied to the *paragraph*
specification (e.g., username may not
access it).   I need to inhibit an Author from using the edit bar if they
are not signed in with the
correct role -- what have I missed, please?

-- 
View this message in context: 
http://www.nabble.com/Security-for-paragraphs--tf4338220.html#a12357504
Sent from the Magnolia - User mailing list archive at Nabble.com.


----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------

Reply via email to