Content Server 6.0 Editor access

Question

I have some cs portlets, some allow you to add/create articles, others are simply "content" spaces using just the rich text field. How can we give access to community managers to change that content without giving them access to the content server explorer?
M

Answer 1

Yeah - I sympathize. Took me a while to get hip to this.
To your point, there are publisher folder objects (and security...) and portal admin folder objects (and security...)
You have a portlet template (in the global portal objects admin folder structure). The user needs to have rights to the template in order to create portlets (also needs rights to underlying web service and server)The portlet template is (by default) bound to a publisher object in a publisher folder (/plumtree/portlet templates/_announcement/en in this case)The portlet templates can have their security bound to the base publisher portlet folders (if you look on security on a publisher portlet instance you'll see this)... this will make more sense later.A user community can create published content in a destination folder in publisher (EX: /plumtree/myAwesomeClient)When the user creates a portlet instance from a portlet template (from the portal admin objects) you tell it your destination folder in publisher (/plumtree/myAwesomeClient) - the act of naming the portlet instance will create (or should create...) a folder with a "like name" - EX: I call my portlet "Eric's test portlet." I should now see... /plumtree/myAwesomeClient/Eric's test portletCool bit... because you've bound the Portlet template's security to the Publisher object's security the user SHOULD be left with admin rights to the content within that new publisher folderConfused yet? :) Took me a while to really grasp this...
What you should get out of this is...
An instance of a portlet (in your global portal admin hierarchy)A publisher folder (in the publisher folder structure)In theory - the two sets of security should be tied togetherThe act of editing the admin prefs on the portlet should automatically update the published content.
I only really figured this out once I wrote my own publisher-based portlet templates. Just step through the idea...
portlet templates are just "links" back to publisher templateswhen you create a portlet from a template security should be tied to the publisher destination folderongoing to let people admin content they need to have rights to...the publisher folder (publisher folder structure)the portlet instance (portal admin folder structure)the users don't need access to the publisher explorer portlet - editing admin prefs on the portlet should be enoughI'm still not sure I explained that very well...
Thanks,
Eric