Details
-
Type:
New Feature
-
Status: Done/Fixed
-
Priority:
Minor
-
Resolution: Fixed/Completed
-
Affects Version/s: 4.7.28
-
Fix Version/s: 4.7.x
-
Component/s: Core CiviCRM
-
Labels:
-
Versioning Impact:Patch (backwards-compatible bug fixes)
-
Documentation Required?:User and Admin Doc
-
Funding Source:Needs Funding
-
Verified?:No
Description
I'm going to create a Send SMS permission that will restrict access to any Send SMS pages and restrict the ability to Send an SMS to people with the send SMS permission.
Attachments
Issue Links
- is duplicated by
-
CRM-21386 Permission to send SMSs (Twilio Extension : org.civicrm.sms.twilio)
-
- Won't Do
-
- links to
Activity
General +1 – it's definitely a better design to provide a distinct permission for sending SMS.
One note: there's a common gotcha in adding new permissions – https://docs.civicrm.org/dev/en/latest/standards/review/#rg-perm – so think about the impact on (a) existing installations and (b) scripted/demo/test sites. If you looked at all the existing sites/users currently running CiviSMS, none of them have the permission configured. When they upgrade, they could lose access to the SMS UI... unless we take some kind of measure to compensate.
In the past, this has usually been handled by adding a post-upgrade-message. (It feels like something better should be possible... but that's what we've got/had so far.)
I think this sounds sensible (Seamus Lee FYI)