In some cases, you may be in a situation when two teams need to moderate the same content for two different displays/use cases. The issue here is that one team may chose to Publish a post to their display, whereas the other team does not want to include it in theirs.
For example, your events team is displaying all of the newest content on a handful of monitors around their venue, and your web team is highlighting only the best content on the event's website. What happens when the events team publishes almost all of the new content as it's aggregated? Unfortunately, it displays on both the venue monitors, and the the event's website.
Given the example above, the setup described below, as well as a slight shift in your moderation workflow, both teams can moderate this content simultaneously.
Create a new Tag for each of the teams. One team can call their tag “Events Published”, the second “Web Published”.
Note: You are not creating these tags when you set up a new Term. Do not automatically apply these new tags to content. Go into Curate > Manage Tags > Create Tag.
Ensure that your current setup is using separate filters for the two teams/displays. Assign the newly-created tags to their respective filters.
Update your terms to auto-publish all content. Note: Don't worry, this will not actually publish the content to your displays.
Provided that these new “-published” Tags are now the only connection to your filters, your content will not be live on any displays until it is tagged with one of the new "-published" tags.
Moving forward your teams will no longer utilize the status buttons (publish, queue, disable) to moderate. Remember, the status of all content is now automatically being set to "Published" by default.
To include a post within a display, your teams will now need to add their respective "-published" Tag to the post.
For example, if your events team finds a post they wish to include on the venue monitors, they will simply apply the "event-published" tag to the post.