Using "Scheduled Actions"

summary you will learn what "scheduled actions" are, how to enable this feature, and how to use them preconditions have a purple editor role in the purple hub have an administrator enable the "scheduled actions" feature for you in your hub see also docid\ xmuoec nufw7yj2tnuzvm docid\ f 1cuygmsg89dhrs1u8fp what are scheduled actions? scheduled actions are times in the future where an article automatically gets modified they are shown and can be managed in the sidebar of the editor, in the "upcoming actions" section currently, we support scheduled publishing, scheduled unpublishing, scheduled access level changes, and changes to article meta fields (see docid\ sfolj8v8qcn3m3jibzbuk ) as actions as seen in the screenshot below, multiple actions can be defined for an article, even multiple actions of the same type this way, complex visibility changes and meta field changes of the content can be planned and configured in advance publishing / unpublishing if the publishing date of the article is set to a date in the future, there will always also be a scheduled publish event in the list of upcoming events corresponding to it but if the article is set to publish "immediately" or is set to a date in the past, no upcoming publish event is shown in the list special case republishing you can use scheduled actions to schedule a "re publish" for your article given an article that is already published (i e it has a publishing date in the past and is already visible to your readers), you can add a new "publish" scheduled action for some date in the future after clicking "update", the article will remain visible, and no change will be visible to your readers but once the selected publish time comes, the date of the article will be re set to that date, making it appear re published access level changes when configuring an access level change, the article will have its access level changed at the selected date and time if the article is published by then (e g manually published, or via an earlier scheduled publish action), the change in access level will also be published and immediately visible in the content cloud and any frontends access level definitions can be configured by administrators in the hub however, modifying existing access levels may affect scheduled actions that are already set up for articles renaming access levels is safe, but changing their order can cause unexpected results custom field changes changing any custom field is also possible, like with a radio field shown below the field will switch to the selected value at the configured time, and the change will also be published automatically if the article is published at the time of change multiple time zone support when the user is another timezone, then the general time zone of the hub then an extra time block is shown showing the scheduled time both in the time based on the hub time zone as well on the time zone of the user migrating to scheduled actions scheduled actions are an opt in feature, meaning existing projects will not have this by default, but it needs to be activated by an administrator on the hub settings page articles that have a configured unpublish date will be migrated to scheduled actions, so that they have an unpublish action on the same time as configured beforehand careful there is no automated data migration for the reverse operation, so when disabling the scheduled actions feature again, posts will have no unpublishing date configured true 330,331 unhandled content type unhandled content type