# How to protect .drone.yml to be updated by anyone apart from admins

**URL:** https://drone.discourse.group/t/how-to-protect-drone-yml-to-be-updated-by-anyone-apart-from-admins/9718
**Category:** Drone Support
**Created:** [March 3, 2018, 7:22am UTC](https://drone.discourse.group/t/how-to-protect-drone-yml-to-be-updated-by-anyone-apart-from-admins/9718 "2018-03-03T07:22:07Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![sandeepsharma](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/sandeepsharma/32/3856_2.png) [@sandeepsharma](https://drone.discourse.group/u/sandeepsharma)
#### Post date: [March 3, 2018, 7:22am UTC](https://drone.discourse.group/t/how-to-protect-drone-yml-to-be-updated-by-anyone-apart-from-admins/9718/1 "2018-03-03T07:22:08Z")

</div>

Hi,

From last two months we are using Drone as CI/CD solutions of our work and i found it very awesome tool in its class.

I have one use case, where i want to know about the best possible solution is possible.

Use Case:  
.drone.yml file should be available in the project repo, as it is expected by drone to execute the pipelines, but problem(not exactly a problem) i see here is that, this .drone.yml can be updated by anyone who has access to that project repo and they can override/comments some of the pipeline steps, which i don’t want to allow.

Hence i want to know about the possible if anything can be done for this use case, so that this .drone.yml file can be by limited or allowed users, even though developers having read/write access to the project repo

Thx

---

<div class="post-metadata">

### Author: ![bradrydzewski](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/bradrydzewski/32/3513_2.png) [@bradrydzewski](https://drone.discourse.group/u/bradrydzewski)
#### Post date: [March 3, 2018, 8:26am UTC](https://drone.discourse.group/t/how-to-protect-drone-yml-to-be-updated-by-anyone-apart-from-admins/9718/2 "2018-03-03T08:26:33Z")

</div>

please see the following threads, are similar in nature and discuss various options:

- [Executing whole pipeline on master branch](http://discuss.harness.io/t/executing-whole-pipeline-on-master-branch/1841)
- [Trigger pipeline defined in Master for other branches](http://discuss.harness.io/t/trigger-pipeline-defined-in-master-for-other-branches/1846)
