Permissions - Granting a User-Level Security Role the ability to create but not modify custom entity.

(0) Share

Report

Posted on by Community Member

Hello;

This may seem like a bit of an odd request, but I have a Custom Entity in my organization, approval for payment, that a set of users need to have the ability to create, but not write to.

The way that Accounting has segmented roles, one group of users has the ability to create these approvals, but a completely different set of users needs to have the ability to modify/approve them only. I have tried granting the Security Role Create and Read as well as Append and Append To privileges at the User level, but when they try and create instances of the entity it fails due to missing Create privileges.

Any help given would be appreciated.

Thanks

Gerry Broderick

*This post is locked for comments

I have the same question (0)

All responses (3)

Answers (0)

ashlega 34,477 on at

Like (0)

Report

Hi Gerry,

could you post a screenshot of the security role settings, and, also, a screenshot of the error message? Also, when they see that error, is there an option to download the log file? If yes, it would be helpful to see the log file as well.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Are you associating the security role with the users directly, or with a Team that they are in? If it is to a Team, then the "User" level Create privilege means that the users will only be able to create an approval record if they remember to change the owner to the Team before they hit Save, because the Team privileges allow them to create records owned by whoever has the create privilege, which is the Team, not the user. If this is the case you either need to make sure users remember to do this, or better still give the security role to the users directly, which will also let the users own the records instead of the team, which sounds better to me in terms of accountability.

Was this reply helpful? Yes No
Suggested answer

prt33k 6,907 on at

Like (0)

Report

Hi Gerry,

You security role setting seems to be fine.

Please make sure the owner field is set to the logged in user while they are creating the record.

Also please share the Error Detail here so that we can look into the exact privileges that are missing and causing error.

It might be possible that some workflow/plugin is trying to update the record on creation which is causing the issue - that will be clear once you share the error detail log.

Thanks,

Prateek

Was this reply helpful? Yes No