# Tk-multi-publish2 show based setting

**URL:** <https://community.shotgridsoftware.com/t/tk-multi-publish2-show-based-setting/11453>\
**Category:** Pipeline Integrations\
**Tags:** fptr-tk\
**Created:** [February 3, 2021, 12:02am UTC](https://community.shotgridsoftware.com/t/tk-multi-publish2-show-based-setting/11453 "2021-02-03T00:02:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ihwangj](https://avatars.discourse-cdn.com/v4/letter/i/6de8d8/32.png) [@ihwangj](https://community.shotgridsoftware.com/u/ihwangj)\
**Post date:** [February 3, 2021, 12:02am UTC](https://community.shotgridsoftware.com/t/tk-multi-publish2-show-based-setting/11453/1 "2021-02-03T00:02:55Z")

</div>

Hello,

What is the best way to handle show-based settings for tk-multi-publish2? For example, show A and show B use the default publish workflow while show C and has their own custom publish workflow?  
It looks like with the current setup, I will need to create a different configuration for each show rather than maintain one configuration for all shows and allow different settings/template for each show.

Thanks,  
Iris

---

<div class="post-metadata">

**Author:** ![philip.scadding](https://sea1.discourse-cdn.com/shotgunsoftware/user_avatar/community.shotgridsoftware.com/philip.scadding/32/30_2.png) [@philip.scadding](https://community.shotgridsoftware.com/u/philip.scadding)\
**Post date:** [February 3, 2021, 8:44am UTC](https://community.shotgridsoftware.com/t/tk-multi-publish2-show-based-setting/11453/2 "2021-02-03T08:44:29Z")

</div>

Hi Iris

That is correct, the normal approach would be to have a different config.  
However it is possible to do a per project configuration in the same config, but it becomes more complicated. I suggest an approach here:

> [@Recommended way to share/update pipeline configurations between projects?](https://community.shotgridsoftware.com/t/recommended-way-to-share-update-pipeline-configurations-between-projects/5609/6):
>
> I thought I’d chime in with a suggestion as well. Option 1 Another approach would be to have a site config (a PipelineConfiguration entity with no project set), using a [distributed setup](https://developer.shotgunsoftware.com/tk-core/initializing.html#distributed-configurations). This will mean that all projects that don’t have their own config will use the site config (you will still need to set a tank\_name value on each Project entity).Then to take over for a specific project, you can just create a PipelineConfiguration for that project. That will be a full config take over though. O…

Best  
Phil

---

<div class="post-metadata">

**Author:** ![ihwangj](https://avatars.discourse-cdn.com/v4/letter/i/6de8d8/32.png) [@ihwangj](https://community.shotgridsoftware.com/u/ihwangj)\
**Post date:** [February 4, 2021, 6:30pm UTC](https://community.shotgridsoftware.com/t/tk-multi-publish2-show-based-setting/11453/3 "2021-02-04T18:30:43Z")

</div>

Thank you, Phil. I read the post and it was really helpful!