web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

How do I restrict workflows to certain users?

(0) ShareShare
ReportReport
Posted on by

I want to limit the edit rights of a certain field to a certain group of people (a custom field that doesn't allow us to restrict it directly) so we thought a work-around would be to make the field read only, create a workflow that changes the field and then restrict that workflow to allow only the people who are allowed to change it.

The only problem with our idea is: I can't figure out how to restrict a workflow to a certain group of people.

I was hoping you could be of help. 

*This post is locked for comments

I have the same question (0)
  • Daniel Wikell Profile Picture
    2,360 on at

    Wouldn't you just want to use field security on that field and assign a field security profile to that group of people? Or do you mean that the custom field you are using is not a CRM field at all but something like a custom html page implementing your own text boxes?

    If you know how to write custom workflow activities you could always write a piece of code that checks if the user running the workflow belongs to a specific team and then fail the workflow if the user does not.

  • Suggested answer
    Mahendar Pal Profile Picture
    45,095 on at

    Hello Lydocia,

    Agreed with Daniel, your requirement is best candidate for Field Level Security, Please refer for field level security details: technet.microsoft.com/.../dn832104.aspx

    Security in workflow handled based on the type of workflow, for example if you have automatic workflow (which triggers based on some event) it is executed based on the workflow owner security context, so if workflow owner don't have edit permission over entity, workflow will fail.

    If you have on demand workflow then it runs based on the current user security role,  so if user don't have edit permission over entity workflow will fail.

    And if it is real time then we can configure Execute As option and you can select if it should run on the security context of the owner of the workflow or the user who made changes to the record.

    Thanks

  • Suggested answer
    Abed Haniyah Profile Picture
    4,287 on at

    Hello lydocia,

    Agreed with Daniel and HIMBAP, But If you want restrict workflow for user or group just put the scope of the workflow to business unit or parent: child business units. However, this isn't likely a good reason to change how your organization is structured in CRM.

    Please refer to : blog.profad.com/.../defining-scope-using-workflows-in-microsoft-dynamics-crm-2011

    Regards,

    Abed.

  • Community Member Profile Picture
    on at

    Hi,

    You could also use a business rules to block or unblock the field to certains users.

    It worked in 2013, haven't tried it yet for 2015.

  • Community Member Profile Picture
    on at

    These fields are implemented by a third party solution we are using, and the field level security on them has been restricted.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans