Share
ReportHello
Which privileges are necessary, that a CRM User can start a Workflow on his own User?
Thank you
Raffi
*This post is locked for comments
You’re offline. This is a read only version of the page.
470
Hello
Which privileges are necessary, that a CRM User can start a Workflow on his own User?
Thank you
Raffi
*This post is locked for comments
Dear all
Thank you for your support and ideas.
I discussed the situation again with the customer and we decided to leave the write-permission for the users on the user-entity. It is a small company and it is ok.
regards
Raffi
Users always have access to their own user record.
Best bet would be to use field level security to prevent people changing this checkbox field (allow read access if they need to do things that depend on it, such as display a view or use a lookup where this checkbox is used as a filter).
Bear in mind that a background workflow (asynchronous) that is run on-demand will always run as the person who initiated it. (A triggered background workflow runs as the owner.) With a real-time workflow you can alter this behaviour, but by the sound of it you will be doing this on-demand, so I would just have this run as a background (asynchronous) one, not real-time.
That way, if a user does have privileges that let them run workflows (because they have those rights for other workflows they need to run) and they run this one, it will run in their context and not be able to do things like modify other user records, or get round the field security.
An on-demand real-time workflow set to run as owner, who is admin, is probably asking for trouble.
Incidentally, how often are you likely to be changing this checkbox for a given user?
I have created an instant-workflow. This runs as Owner of the workflow. The owner is a sysadmin.
The workflow will set a checkbox active or inactive on the user record.
I do not want allow the users to change their own user. So I thought, this is a practicable way... What do you think?
Hi Raffaele,
It should have write ,create, update (the operation you performing) permissions to the entity you working with.
It depends what you are doing in that workflow. First of all if the workflow is going to make changes in the user record. Then the user must have read/write permissions on user entity. Then to run a workflow, the user need permissions to read/append/append to the process, may be create process session permission and execute workflow job as well (under customization tab). If there is any plugin involved then read permission for plugin assembly and there are many more permissions based on your requirement. Hope this helps
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
All responses (
Answers (