News Creater in complex Hubsite

%3CLINGO-SUB%20id%3D%22%5C%26quot%3Blingo-sub-3157866%5C%26quot%3B%22%20slang%3D%22%5C%26quot%3Ben-US%5C%26quot%3B%22%3ENews%20Creater%20in%20complex%20Hubsite%26lt%3B%5C%2Flingo-sub%26gt%3B%3CLINGO-BODY%20id%3D%22%5C%26quot%3Blingo-body-3157866%5C%26quot%3B%22%20slang%3D%22%5C%26quot%3Ben-US%5C%26quot%3B%22%3E%3CP%3EHello%2C%26lt%3B%5C%2FP%26gt%3B%3C%2FP%3E%3CP%3Eusing%20a%20complex%20Hubsite%20construct%2C%20each%20Department%20has%20own%20Sitecollection%20as%20Sub%20of%20the%20Hubsite.%3CBR%20%2F%3EOn%20each%20department%20there%20are%20a%20view%20news%20creater%20designated.%26nbsp%3B%3CBR%20%2F%3EPer%20default%20when%20i%20add%20the%20necessary%20persmission%20to%20create%20news%20these%20group%20are%20able%20to%20do%20a%20lot%20more%20than%20just%20creating%20news.%3CBR%20%2F%3EIs%20there%20a%20option%20to%20prevent%20this%20and%20just%20allow%20creating%20news%3F%3CBR%20%2F%3E%3CBR%20%2F%3EWhen%20i%20brake%20the%20interheritance%20of%20the%20sitepage%20library%20and%20add%20the%20group%20there%20they%20able%20to%20add%20%22other%22%20sites%20as%20well.%20I%20am%20not%20able%20to%20create%20a%20dedicated%20Sitepage%20library%20just%20for%20news.%26lt%3B%5C%2FP%26gt%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%26lt%3B%5C%2FP%26gt%3B%3C%2FP%3E%3CP%3EPlease%20advice%2C%20workarounds%20are%20welcome%20as%20well.%26lt%3B%5C%2FP%26gt%3B%26lt%3B%5C%2Flingo-body%26gt%3B%3CLINGO-LABS%20id%3D%22%5C%26quot%3Blingo-labs-3157866%5C%26quot%3B%22%20slang%3D%22%5C%26quot%3Ben-US%5C%26quot%3B%22%3E%3CLINGO-LABEL%3EDocument%20Library%26lt%3B%5C%2Flingo-label%26gt%3B%3CLINGO-LABEL%3EPermissions%26lt%3B%5C%2Flingo-label%26gt%3B%3CLINGO-LABEL%3ESharePoint%20Online%26lt%3B%5C%2Flingo-label%26gt%3B%26lt%3B%5C%2Flingo-labs%26gt%3B%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3C%2FLINGO-SUB%3E
Occasional Contributor

Hello,

using a complex Hubsite construct, each Department has own Sitecollection as Sub of the Hubsite.
On each department there are a view news creater designated. 
Per default when i add the necessary persmission to create news these group are able to do a lot more than just creating news.
Is there a option to prevent this and just allow creating news?

When i brake the interheritance of the sitepage library and add the group there they able to add "other" sites as well. I am not able to create a dedicated Sitepage library just for news.

 

Please advice, workarounds are welcome as well.

2 Replies
Error: MigrationPermanentException: The target mailbox doesn‎'t have an SMTP proxy matching ‎'mail.xyz.com.bd‎'. --> The target mailbox doesn‎'t have an SMTP proxy matching ‎'mail.xyz.com.bd‎'. Anyone has got this kind of errors above while migration from o365 cloud to on-prem local exchange? Please share your knowledge.
I can think of two options to get more control over news posts: You will need to implement each option on each site in your hub family.

Option 1. Add an approval workflow for all pages and then automatically approving “regular” pages but requiring news pages to be approved prior to publishing. You can do this with a condition on the workflow based on the Promoted State attribute of the page. Promoted State =0 are regular pages. All other pages are draft news articles (Promoted State =1) or published news (Promoted State=2). It is not quite the same as only giving permissions to write news pages, but it ensures that there is a review by designated approvers prior to publishing.

Option 2. Create a separate site for publishing news pages and use that as the source for the news web part on your main site. Only designated users can create news on the main site but on the News site, you can open up edit permissions. In this scenario, users would need to follow the News site and the main site to have news show in their personal feeds, but it would allow you to isolate the permissions for news authoring very easily.