I get this - We Have a few Global Process Templates that are the same for every Client. We need to make a change to the Global Process so that all the individual Client Processes reflect the change. Even If there was a way to Link a Global Process to an asset like a user Directly without having to assign the process to the Client first would help.

I think this could be handled quite easily with an option to add a Process as a linked process or a free process when it's created at the company/client level. You could also default to linked, and have the linked property change if the process is edited at the client level.

Also a way to view which clients have cloned a global process template, and which are linked vs free would be a huge help in managing and updating processes.

We need a way to keep the child processes up-to-date.

Just had this similar thought. We have a use case where you have to go to another location to look up a credential in another system. It would be great if we could create the global KB item and then allow it to be visible on the client level in an updated manner.

Also, the ability to select if it should be part of an export or not for that client.

We have global processes that change frequently, and when we do that, we have to remove the process template from a slough of clients make changes to the Global process, then re-add the template. Dynamic updates to Global processes down to client templates is needed!!

We Agree, this is super important to keep processes upto date.

I think it's critical to allow the refreshing of downstream templates. We're testing the use of a template to track security best practices. If we can't refresh the templates from the master, none of the older clients will have the new checklist items. There will be no way to reconcile and go back to determine who needs attention. With auditing in place as it is, the risk should be pretty low. If the checklist item changes, ask if you want the change propagated and if so, store the original item name in the audit trail. Without this, we need an option to modify the company assets and create instances of related metadata fields in those records to track these items.

The way to do this would be to create a relationship with tasks between the global and client templates.

In the event a task was modified on a client level it would break the relationship; when modified on the global level it'll update everywhere else as well. When the process itself was modified (structure changed or tasks added/removed) it'll update on all linked processes.

Maybe any that haven't been customized should automatically update and any that have been customized shouldn't, but you should have the option