CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviCase (Moderator: Dave Greenberg) »
  • Permissions within CiviCase - on a per-casetype basis
Pages: [1]

Author Topic: Permissions within CiviCase - on a per-casetype basis  (Read 504 times)

nickholden

  • I post occasionally
  • **
  • Posts: 111
  • Karma: 1
  • CiviCRM version: 4.4.1
  • CMS version: Drupal 7
  • MySQL version: 5.5.32
  • PHP version: 5.4
Permissions within CiviCase - on a per-casetype basis
September 19, 2013, 06:19:18 am
We'd like to be able to restrict access (certainly create / edit / delete access, view access is less of an issue) to teams of staff who deal with particular case types. Currently it seems that CiviCRM ACLs apply only to contact, events, profiles and custom data, and therefore cannot be defined to apply to CiviCase data, never mind specific case types.

Has anyone got a handle on what would be involved in applying the ACL concept to CiviCase, particularly in a way that would enable us to allocate staff into a group with permision to work on cases of a specific case type (analagous to the way the 'group of contacts' ACL can be used to give only certain users the ability to edit contacts in a specific group)?

Thanks in advance.

Nick

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Permissions within CiviCase - on a per-casetype basis
September 19, 2013, 07:18:05 am

If i were doing it, i would approach it as follows (for minimal work):

a. Check the code and figure out where you need to add access control. Typically in most civi code this is in 1-5 places (i.e. not all over the place)

b. Invoke the existing hook so an external module can send in the ACL query clause (Civi has an acl hook for this that u can most likely reuse)

c. Implement a module with the hook

If i had to guess, this is a 10-20 hour project?

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviCase (Moderator: Dave Greenberg) »
  • Permissions within CiviCase - on a per-casetype basis

This forum was archived on 2017-11-26.