I have created a Quick Action button, that basically calls a webservice and displays the data in a popup window.

Right now, I only want certain users to have access to the Quick Action button.

I don't want to create a new Profile for these users, and assign a new page layout to the new Profile because eventually everyone will have access to the Quick Action.

I was thinking of Permission Set, but that does'nt seem to address my use case, unless i am missing something.

Does anyone have other suggestions?


I am not sure if it is the best approach, but I had a situation very close of that where i had created custom field called as EnableFeature__c with field type checkbox in User object for storing value to enable this feature.

In lightning controller js doInit function, I'm calling apex class where logic was to get current user data using SOQL and checking this field and returning the boolean result. Based on the result i was displaying the message to user as custom toast message because standard toast message wont supported in Lightning quick action.

  • Thanks @ChetanNandre. That's a good work around however, not the best approach (as you guessed) for my use case. – GroundToCloud Sep 19 '19 at 15:02

Why don't you add a user name check in your code, so that way, it will be only useful for the users intended to else it will not work or just show a friendly error saying this feature is not available for you.

I know this seems to be a work around and not a solution. But without profile and pages, this is something I can think of.

  • Thanks @AmitSahu for the response. In few weeks everyone will have access to the Quick Access Button, hence I don't want to handle it in the code, and was hoping I could handle it through Configuration. – GroundToCloud Sep 13 '19 at 16:35
  • 1
    @user4947 (This is just an option, but for your use case this does not make sense to have this much work just to throw it out. Sharing it. if someone might want to have a long term solution). This can be only achieved with custom code then. You will have to create the entire page again and add the permission set code, which will then render the buttons.That's being said, there is no out of the box feature to support your case. – Amit Sahu Nov 18 '19 at 15:53
  • Thank you @Amit Sahu for revisiting my post. – GroundToCloud Nov 18 '19 at 16:57

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.