# Lock provider event

**URL:** <https://community.open-emr.org/t/lock-provider-event/5310>\
**Category:** OpenEMR Development\
**Created:** [June 25, 2013, 8:20pm UTC](https://community.open-emr.org/t/lock-provider-event/5310 "2013-06-25T20:20:10Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [June 25, 2013, 8:20pm UTC](https://community.open-emr.org/t/lock-provider-event/5310/1 "2013-06-25T20:20:10Z")

</div>

**[pfindan](https://sourceforge.net/u/pfindan/)** wrote on [Tuesday, June 25, 2013](https://sourceforge.net/p/openemr/discussion/202506/thread/31948588/#fedf):

Hi all,

Recently one of my clients asked for the ability to create a provider event that front office staff could not delete. I have looked around for a while now and can not seem to find a way to do this. If any of you know how I would go about this I would appreciate it greatly. I don’t mind coding something of you could let me know how you handle user access control in OpenEMR.

Thanks a lot!  
Daniel

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [June 26, 2013, 5:49am UTC](https://community.open-emr.org/t/lock-provider-event/5310/2 "2013-06-26T05:49:10Z")

</div>

**[visolveemr](https://sourceforge.net/u/visolveemr/)** wrote on [Wednesday, June 26, 2013](https://sourceforge.net/p/openemr/discussion/202506/thread/31948588/#91a5):

Hi,

This can be accomplished by controlling the access rights of the front office staff who logs in.

Go to “Administrator-\> ACL” under “Groups and access Control-\>Front Office-write” you can define the items that front office can access under **“Active”** section and others(items they should not access) under “Inactive” section.

Hope This Helps.

Thanks,  
Your OpenEMR Customization/Support provider,  
ViSolve,Inc  
[services@visolve.com](mailto:services@visolve.com)

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [June 26, 2013, 1:59pm UTC](https://community.open-emr.org/t/lock-provider-event/5310/3 "2013-06-26T13:59:18Z")

</div>

**[pfindan](https://sourceforge.net/u/pfindan/)** wrote on [Wednesday, June 26, 2013](https://sourceforge.net/p/openemr/discussion/202506/thread/31948588/#2ae0):

Thanks for your reply. I looked into the ACL for front office staff, but I can not seem to find a way to allow them to delete patient appointments, but to not be able to delete provider appointments/events. I can only turn all appointment deletion off. How would I make it so the Front Office cannot delete Provider Events?

Thanks!  
Daniel

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [June 26, 2013, 3:09pm UTC](https://community.open-emr.org/t/lock-provider-event/5310/4 "2013-06-26T15:09:54Z")

</div>

**[drkay](https://sourceforge.net/u/drkay/)** wrote on [Wednesday, June 26, 2013](https://sourceforge.net/p/openemr/discussion/202506/thread/31948588/#c909):

I have the same problem in my office. In order for my staff to be able to do basic things they need to do, like correct an error that they made in entering a patient weight, I have to give them the ability to delete things they shouldn’t be able to delete. Can we make ACL more nuanced?

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [June 27, 2013, 6:55am UTC](https://community.open-emr.org/t/lock-provider-event/5310/5 "2013-06-27T06:55:08Z")

</div>

**[bradymiller](https://sourceforge.net/u/bradymiller/)** wrote on [Thursday, June 27, 2013](https://sourceforge.net/p/openemr/discussion/202506/thread/31948588/#2162):

Hi,

ACL has a huge amount of room to grow. Developers can add/expand/modify ACO/ACL’s and integrate them into the code(including the official codebase), which is discussed here:  
[http://www.open-emr.org/wiki/index.php/PhpGacl](http://www.open-emr.org/wiki/index.php/PhpGacl)

-brady  
[OpenEMR](http://www.open-emr.org/)

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [June 29, 2013, 1:06pm UTC](https://community.open-emr.org/t/lock-provider-event/5310/6 "2013-06-29T13:06:34Z")

</div>

**[pfindan](https://sourceforge.net/u/pfindan/)** wrote on [Saturday, June 29, 2013](https://sourceforge.net/p/openemr/discussion/202506/thread/31948588/#46eb):

Thanks for the link. I am going to begin work on a acl group for this. Will let you know how I do.

Thanks!