Team-based / Role-based permissions on Action Buttons?

Hello,

Is there a way to set team-based or role-based authorisations on the action buttons?

I have built a button that should only be made available in the subpanel as a dropdown and the action behind it should perform a field value change. Everything works fine, but the function button should only be available for certain teams and/or roles. Is it possible to introduce these restrictions?

Many thanks in advance for your feedback.

Martin

---------

12.0.4 ENT
On Premise

  • Hey  

    Action buttons behave somewhat like a new field, so you should be able to apply Roles permissions at the field level to them. See here

    When that's not enough, you always have the option to create a customisation to suit your exact needs.

    Hope it helps

    --

    Enrico Simonetti

    Sugar veteran (from 2007)

    www.naonis.tech


    Feel free to reach out for consulting regarding:

    • API Integration and Automation Services
    • Sugar Architecture
    • Sugar Performance Optimisation
    • Sugar Consulting, Best Practices and Technical Training
    • AWS and Sugar Technical Help
    • CTO-as-a-service
    • Solutions-as-a-service
    • and more!

    All active SugarCRM certifications

    Actively working remotely with customers based in APAC and in the United States

  • Hi Enrico,

    thanks for your feedback, but the Action Field does not appear in the Role Configuration. If I want to add access at php level on a role basis, how can I go about this?

  •  fair enough, sorry for misleading you. I was going by what the documentation mentions about action buttons and roles, teams and access control. Based on that, you could create a support ticket and a bug to either fix the documentation or the behaviour.

    As action buttons are something mostly based on the front-end, I'd attempt to customise the sidecar javascript views/fields to see if there is something you can do there.

    If that's not a working route, I'd create your custom buttons, which you would have full control of. Then by retrieving the current user from the js side, you could show the custom button or hide it based on specific information and rules.

    --

    Enrico Simonetti

    Sugar veteran (from 2007)

    www.naonis.tech


    Feel free to reach out for consulting regarding:

    • API Integration and Automation Services
    • Sugar Architecture
    • Sugar Performance Optimisation
    • Sugar Consulting, Best Practices and Technical Training
    • AWS and Sugar Technical Help
    • CTO-as-a-service
    • Solutions-as-a-service
    • and more!

    All active SugarCRM certifications

    Actively working remotely with customers based in APAC and in the United States