cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
%3CLINGO-SUB%20id%3D%22lingo-sub-588794%22%20slang%3D%22en-US%22%3EPublic%20accessible%20content%20vs%20private%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-588794%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20want%20to%20be%20able%20to%20dictate%20whether%20an%20article%20requires%20a%20sign%20in%20or%20not%2C%20so%20we%20don't%20have%20multiple%20boards%20with%20different%20permissions.%20As%20in%2C%20some%20content%20we%20might%20deem%20public%20and%20some%20behind%20the%20sign%20in%20wall.%20Is%20there%20a%20way%20of%20doing%20this%20at%20article%20level%20at%20all%3F%20Using%20Labels%20or%20Tags%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Advisor

Public accessible content vs private

We want to be able to dictate whether an article requires a sign in or not, so we don't have multiple boards with different permissions. As in, some content we might deem public and some behind the sign in wall. Is there a way of doing this at article level at all? Using Labels or Tags?

1 Reply 1
Highlighted
Honored Contributor

No, not without heavy customization. Khoros doesn't have content-level permissioning. It's all done at node (board/category) levels.

Anything's possible, of course, but it really would require extensive customizations which you'd then have to test / support for every upgrade thereafter. You should weigh the overhead on that vs. just having the content on boards with the appropriate permissions.


Becky Scott