User Access / App Permission Settings

June 15, 2014

Ideally, SMS Magic application should be installed with “Grant access to all users” option. Even after that, if all users are unable to access SMS Magic application, please follow the below mentioned steps.

1. Custom App Settings
2. Custom Tab Settings
3. Custom Object Permissions
4. Save the profile and assign it to user
5. Check for the Visualforce Page permission
6. Check FLS permission of SMS Magic Objects

Suppose you want to enable SMS Magic for a user having a standard profile, e.g. “Standard Platform User”. You will have to create a clone of this profile and edit the permissions for SMS Magic as mentioned below. This is because permissions are non-editable in standard profiles.


Edit Profile

Give proper name to profile and save it.

Change Profile Name

Change Profile Name

Now click on  “edit” on the custom profile created.

Edit Custom profile

Edit Custom profile


Provide the following permissions:

1. Custom App settings – Please ensure that SMS Magic Interact or Basic is “visible” to the profile.

Give appropriate Permissions

Give appropriate Permissions

2. Custom Tab Settings – Please make sure that the tabs related to SMS Magic are visible.

Custom Tab Settings

Custom Tab Settings

3. Custom Object Permissions –  Please give modify all permission to SMS Magic objects as follows:

Custom Object Permission

Custom Object Permission

4. Save the profile and assign to user – Save the profile and assign it to the user to whom you want to give acess to our package.

5. Check for the permission – Check if the custom profile created has the permissions for accessing the SMS magic Visualforce pages.For this goto Setup—>App Setup—>develop—>Pages

Permission for SMS Magic VF pages

Permisssion for SMS Magic VF pages

Filter all the sms magic pages.Click on “Security” of each page one by one.

Per Page Security

Per Page Security

The desired profile should be there in the enabled profiles list of that page.

Enable permission for VF page

Enable permission for VF page

Now user should be able to access SMS magic Objects /Tabs and also the send SMS facility to whom this new profile is assigned.

Also make sure that user is having permission for all fields of objects from SMS Magic Interact package as well as the fields of objects which are involved for sending SMS.


6. Check FLS permission of SMS Magic Objects – In addition to this, you need to give FLS (Field Level Security) access to below custom objects and the respective fields from profile page itself:

  1. SMS History
  2. SMS Sender Id
  3. SenderId Profile Map
  4. SMS Templates
  5. SMS Template Type
  6. Incoming SMS
  7. Action On Incoming SMS
  8. Incoming Lookup
  9. Incoming Alert Configuration
  10. Opt-out Setting

To do the same:

  • Go to profile UI to which you want to give access to SMS Magic—In the Field-Level Security section, click View next to the object you want to modify, and then click Edit.
    profile UI
  • Specify the field’s access level to “visible”.
    Specify the field's access level to "visible"
  • Click Save.
    You can also check FLS permissions for above given object from Setup–>Security Controls –>Field Accessibility. E.g.
    FLS permission Field Accessibility

Push SMS Callout – In order to send SMS from custom code user need to have permission to SMS history object.

Jun’15 release additional permissions

SMS Magic Interact (June’15) provides you additional permissions.

User needs to have additional permission to send SMS from bulk and campaign.

If user doesn’t have sufficient permission to “Read” any merge fields of SMS template during sending message then following error message will be displayed.

“You do not have permission to render fields of {{objectname}} template”

Related Posts

Sender ID
SMS on Workflow
Incoming SMS Related List

No comments

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>