Schedule product updates

@Anitahg you can schedule Articles, but not other content types. Maybe give that a try for your release notes and documentation needs (your tech writers will need access to Control to do this).

Thanks @Scott Baldwin sorry I should have been more precise here. My question is if it is possible to schedule Product Updates to go in the Product Updates section. Our tech writers have access to Control, but they miss the possibility to schedule posts. 

Ok, that’s not possible I believe. We don’t use Product Updates that inSided offers, and instead use a category with only employee permissions to post 

@Cristina you may want to re-title this to “Schedule Product Updates”

This is starting to become a pain point. Hope it gets considered for improvements sooner than later. 

@DannyPancratz just shift from product updates to a category and use articles which can be scheduled.

@Cristina any update on this idea? if it will not be delivered upon soon we will have to stop using this category and switch to a category and use articles as @Scott Baldwin suggests. 

Unfortunately, I do not have any updates on this request and I don’t foresee an opening in our planning short term to include this improvement. However, it does remain a high priority for us to fill this kind of functionality gaps, we just need to address first some underlying technical complexities. 

Just to chime in, this feature would be very helpful for us as well. More info. on our use case if its helpful:

• We now use Product Updates to announce all product releases
• When we do quarterly launches (rolling up multiple releases typically), we have multiple communications about the releases scheduled to go live in a coordinated fashion (e.g., blog post, email, in-app messages, social, etc.)
• Since most of the launch comms. reference the Product Update posts in the community for additional details, it’s challenging to now be able to schedule posts in advance AND to not have a URL for the posts in advance (not sure if these would be two separate features or combined); having the URL in advance would be very helpful, so we could include it in all of our other launch comms. that are scheduled