Announcement

Collapse
No announcement yet.

Commit security by client groups

Collapse
X
 
  • Filter
  • Time
Clear All
new posts

    Commit security by client groups

    We need to be able to limit employee access based on groups not individual companies. Nobody has time to add individual companies to an access list.

    We use the Ctype list to segregate customers based on which division of the company they do business with. We want to use this same list to allow access for staff.

    Staff who are on the residential side don't need access to commercial client in CommitCRM. Typically commercial can do both, but not the other way around.

    How can we setup access restrictions based on groups?

    We discovered someone on the sales side of our division, was calling customers in another division. Nothing malicious (other than being a pesky salesman) but if we could limit access based on the customer groups we already have setup this wouldn't be an issue.

    It would also go a long way towards have a more secure, segmented system.

    Re: RangerMSP security by client groups

    Thanks for the clear feedback and explanation. It seems like you are familiar with what's possible and want to streamline it into group selections. The request is clear and we will consider it. Thanks.

    Comment


      Re: Commit security by client groups

      Is there some custom code I can do to make it happen? Something generally unsupported but will work.....

      I really need this (if you couldn't tell.)

      Comment


        Re: RangerMSP security by client groups

        we could tell ;) No hack to recommend though.

        Comment


          Re: Commit security by client groups

          Could we enable a feature where techs get access only to the accounts of tickets assigned to them?

          That would also require some controls on who can assign tickets to them.

          Then things would be easier to manage.

          Comment


            Re: RangerMSP security by client groups

            What you suggest is dynamically allowing access to account based on ticket assignments. We see several complexities here but we'll take a not on this. the way it works now with access to tickets (as you know) is that each user is assigned with a privileges group that sets what they can and cannot do or access. When techs do not have the privilege to access Other Employees' Tickets they won't be able to access such tickets, though this has no effect over accounts (to which you can limit access to specific accounts, when the web interface only is used).

            Hope this helps and thanks for your suggestion.

            Comment

            Working...
            X