# Developers overwrite each other Slicemachine syncs

**URL:** <https://community.prismic.io/t/developers-overwrite-each-other-slicemachine-syncs/11989>\
**Category:** Developing with Prismic\
**Tags:** nuxtjs, slice-machine\
**Created:** [December 14, 2022, 8:57pm UTC](https://community.prismic.io/t/developers-overwrite-each-other-slicemachine-syncs/11989 "2022-12-14T20:57:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![SebastianGebhardt](https://avatars.discourse-cdn.com/v4/letter/s/2acd7d/32.png) [@SebastianGebhardt](https://community.prismic.io/u/SebastianGebhardt)\
**Post date:** [December 14, 2022, 8:57pm UTC](https://community.prismic.io/t/developers-overwrite-each-other-slicemachine-syncs/11989/1 "2022-12-14T20:57:01Z")

</div>

Hello everybody,

i have a tiny question about the workflow with a team on the sicemachine.

We have some mutiple branches in our github repo. Each developer is working on his own branch with his own feature. Now at the moment is possible that developer A make a commit of his changes to [prismic.io](http://prismic.io). Developer B make some changes as well on a other branch. Develoeper B commit his changes also to [prismic.io](http://prismic.io) and overwrite the slice-zone, the fields and the current data on a document of this custom post type.

How we can avoid this issuse? what is a best practices for this problem?  
Thanks for your help! 🙂

---

<div class="post-metadata">

**Author:** ![Pau](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/pau/32/5422_2.png) [@Pau](https://community.prismic.io/u/Pau)\
**Post date:** [December 14, 2022, 10:14pm UTC](https://community.prismic.io/t/developers-overwrite-each-other-slicemachine-syncs/11989/2 "2022-12-14T22:14:26Z")

</div>

Hello @SebastianGebhardt, we've had similar discussions before here on the forum. [Here's our take on this particular topic:](https://community.prismic.io/t/working-on-the-same-prismic-page-in-multiple-branches/11454/3)

> [@Working on the same prismic page in multiple branches](https://community.prismic.io/t/working-on-the-same-prismic-page-in-multiple-branches/11454/3):
>
> There is no option to limit who modifies the Custom Type models in a repository that uses Slice Machine. If in dev has access to the project code and repository, it is possible to change everything.
> 
> The git version control must go hand in hand with a good communication system between the teams. Doing code reviews is necessary so that these types of errors do not exist.

Let us know if you have any comments or thoughts about this subject.  
Thanks