Business Problem: Client wants a specific client defined role to be able to answer administrative questions on the general application. However, by granting this permission to a role, the ability to force apply applicants to an opportunity is also granted. The customer does not want this role to have the latter functionality.
One suggestion: Permission structure for roles is currently bundled into packages. Unbundling these permission sets and allowing for a more granular selection of permissions would solve the customers problem, so that the ability to answer administrative questions can be independent from granting the ability to force apply applicants.
Employee Name | Micco Fay |
Client Name "shard name" | auburn, humsci-stanford |
User | System Admin |
Functional Unit | Client-Defined Roles |
humsci-stanford would also like this feature. Their particular use-case: They have a client defined role that they would like to give View Only permission to for Post Acceptance, however they would still need them to be able to access and categorize applications within the Automatch and Apply-to bulk actions grids. These two permissions are currently lumped together. We looked into restricting all Post Acceptance categories, however these users process renewals and need access to the Awarded renewal category which is also lumped together.