# Locking - I can't turn the locking feature off

**URL:** <https://connect.superhuman.com/t/locking-i-cant-turn-the-locking-feature-off/20036>\
**Category:** Ask the Community\
**Created:** [December 10, 2020, 5:23pm UTC](https://connect.superhuman.com/t/locking-i-cant-turn-the-locking-feature-off/20036 "2020-12-10T17:23:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tom\_Flynn](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/tom_flynn/32/18335_2.png) [@Tom\_Flynn](https://connect.superhuman.com/u/Tom_Flynn)\
**Post date:** [December 10, 2020, 5:23pm UTC](https://connect.superhuman.com/t/locking-i-cant-turn-the-locking-feature-off/20036/1 "2020-12-10T17:23:26Z")

</div>

I copied a Coda doc that is on a Team plan and put it in my folder which does not have a team plan. Coda sent me an error message, attached, that says I need to turn off locking or upgrade otherwise the doc will become read only in 14 days, as locking is a team feature.

![image](https://global.discourse-cdn.com/coda1/original/3X/d/5/d5ea40d385497e1f7c626189aa9930f5fc3133a4.png)

It appears there’s no way to turn locking off. All of the locking settings are greyed out and can’t be changed, likely because I’m not on a team plan.

Has anyone else dealt with this and solved this or does anyone know a potential solution?

I’d like to turn off locking for a doc that has it turned on on a non-team plan where all locking settings are disabled.

---

<div class="post-metadata">

**Author:** ![Ben\_Lee](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/ben_lee/32/49867_2.png) [@Ben\_Lee](https://connect.superhuman.com/u/Ben_Lee)\
**Post date:** [December 11, 2020, 1:29am UTC](https://connect.superhuman.com/t/locking-i-cant-turn-the-locking-feature-off/20036/2 "2020-12-11T01:29:12Z")

</div>

Hi @Tom_Flynn,

Welcome to the community!

And thank you for the feedback. This looks like a bug. I’ve added it to our internal tracker and the team has seen it. I don’t have an ETA for a fix yet, but it is being looked into.

Thank you for reporting it!
