Forums - Thread Details
  • State Verified Answer
  • Replies 7 replies
  • Subscribers 320 subscribers
  • Views 1096 views
  • Users 0 members are here
Forum Actions
Related

How to control access on dashlets

Jeroen Somhorst

Hi, 

for a specific use case we would like to be able to control the access to dashlets. Currently , as far as I know, there is no way of configuring this. So any user can select the dashlet and we need to implement logic in de controller of that dashlet to find out if the current user is allowed to use it. 

I wonder if there is a different approach to accomplish this task. For instance for a certain dashlet prevent it from showing in the dashlet list. 

Is this possible?

Parents
  • +1

    ,

    Normally when you build a custom dashlet, you also have a custom api that goes with it, to retrieve from the backend the data you need to show.

    As you correctly hinted at, on the backend api side you would do all your check and balances (can the user see what will be shown? can the user act on what is presented the them?) and return the correct data to the UI part.

    Then on the UI part you can show relevant message (ie: an empty dashlet with a self-explanatory message, or the standard message used throughout the system "No data available.").

    Basically, any user would be able to add the dashlet, but it will not show anything (or potentially show partial information) for the users that are not supposed to have access.

    That's how I would implement it.

    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

Reply
  • +1

    ,

    Normally when you build a custom dashlet, you also have a custom api that goes with it, to retrieve from the backend the data you need to show.

    As you correctly hinted at, on the backend api side you would do all your check and balances (can the user see what will be shown? can the user act on what is presented the them?) and return the correct data to the UI part.

    Then on the UI part you can show relevant message (ie: an empty dashlet with a self-explanatory message, or the standard message used throughout the system "No data available.").

    Basically, any user would be able to add the dashlet, but it will not show anything (or potentially show partial information) for the users that are not supposed to have access.

    That's how I would implement it.

    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

Children
No Data