Hi,
despite we see and configure in roles the access for PMSE Emails Templates, the standard users can't access to the module. We need the users to be able to select in a relate the appropriate email template.
currently we see that acl is forced to "no access" for all non-admin users for this module.
is it possible to remove this "lock" ?
The SugarBPM Email Templates are intended to only be used for SugarBPM email actions within a process definition. What benefit or use case are you looking to achieve by having non-admin users view these templates?
Chris
Currently the only way I am aware of granting access to Process Email Templates is by either making the user a full admin or giving them 'Developer' role access on one or more modules. When using 'Developer' access, this gives the user ability to only create/modify SugarBPM-related items for the module(s) for which they have that role access. It also grants them ability to make changes to the module(s) through Studio so this permission is not something you want to grant to users with limited knowledge of Sugar.
For your second use case, the Developer role access would seem most appropriate as users charged with modifying those templates ultimately need to be able to look at the process definitions to understand which templates are used and how changes to a template may impact multiple processes using the template.
For the first use case, it doesn't sound like this is a viable method and it would likely be better to develop a standalone module with similar functionality rather than trying to use the existing module for unintended uses. There is an enhancement # 88925 currently filed for opening process modules to typical role access, so I recommend filing a support case with SugarCRM to have it associated with that enhancement.
