Improved permissions for activities and cases

Veröffentlicht
2014-10-10 11:39
Written by
pmoz - member of the CiviCRM community - view blog guidelines

A little background.

Established in 1972, we are a non-profit human services organization that serves many diverse populations in the Greater Pittsburgh area.

A large part of our focus is on homeless services, but we also do some mental and physical health programming, early childhood development, community integration and host a large food pantry near the University of Pittsburgh campus. 

Because of our disparate clientele and locations, we have been using multiple Access databases to track participant information.  For many years we wanted to move it online so staff in people's homes, could enter updates from the field.  However, the cost to implement was prohibitive to say the least.

Our Drupal and CiviCRM experience

When we rebuilt our website using Drupal, I stumbled upon CiviCRM as an alternate to Constant Contact.  For two years, we have used Civi on the backend of our site to register for events, make online contributions and send out bulk mails.

Civi has helped us raise a lot of dough.

After working in Civi and Drupal, we realized the combination could effectively be used to consolidate our program and human resources data as well as make it available online.

So we set off on the challenge of implementing a database to track all of our program's data, but repeatedly were having to reinvent the wheel to avoid staff seeing information that had nothing to do with their program.  Since the site was not for the public, we wanted to limit all work in Drupal (i.e: creating views and webforms), and instead focus on streamlining the database.  In essence, Drupal became the backend and Civi the front.

However, the Drupal permissions for CiviCRM were too general to control access to Activities and Cases and while the ACLs in Civi do provide more granular security, they don't cover Activities and Cases.

Make it Happen

We began rolling out our shiny new database in July 2014.

During the roll-out, I began investigating the cost of adding security to Activities and Cases and stumbled upon some threads discussing it.

This one that started in 2009 got me going and we haven't looked back since.

With these changes, it becomes dramatically easier for non-profits like us to implement CiviCRM as a total solution.

Thanks to Donald Lobo and Michael McAndrew for their guidance.

Please share your thoughts.

Comments