We created a new module via Module Builder. We have a custom ACL defined in custom/data/acl. We do not want the new module to be visible in the Roles as we have a custom ACL. How can we exclude the module from appearing in Roles?
Hi, i would like to hide Custom Queries and DataSets for non-admin users. Is there any way, that i can do this under custom/modules/CustomQueries and custom/modules/DataSets ? Thanks!! Samer Kaskas
Hi everyone.
I want to just check if this is a bug or not. I have created a "Admin" role which has Admin and Deveolper access to all modules. However this user when going into "Manage Dashboards" cannot edit a dashboard that isn't theirs meaning they…
in sugarcrm i have a user with 2 roles - one admin and other custom role , when i login as that user , it doesnot let me access create permission in one module , if i assign user , it is working fine ,
in studio for custom role - that module create…
Hi everyone.
Maybe a simple question, but wanted to confirm. Looking at roles on the front end "Edit" ties into both Edit and Create. We have scenario where the customer would like to edit records but doesn't want anyone creating any (As they come in…
Hi everyone, We've been using Git to deploy Sugar code on premise for a while now, and since my customer started playing with role-based views, I ask myself this question : Should I keep versioning those views? The obvious answer is "Yes, you should,…
Our Sugar 8.3 instance is integrated with another application (ServiceNow) using REST API, where data is sent from Sugar to ServiceNow, and ServiceNow record ids are saved in Sugar modules. If the API logs into Sugar as a non-admin user, then Sugar does…
Hi, Bit of an odd one this. We have a main status field and a sub status field. The status is the parent dropdown and determines what to show in the sub status (via studio). The sub status is however role based. The bug is that a user who shouldn't be…
The Assigned To field in our clients module is set to Read Only for the sales agent role because we don't want the agents to be able to change that field at all. What I need to do is find a way during the creation of a new client to run a hook - or part…