Showing results for 
Search instead for 
Did you mean: 

Restrict Guided Sourcing User to create requests only

0 Kudos

Dear All,

can someone tell me how to restrict user from creating guided sourcing projects?

We set up guided sourcing requests and projects. GS Requests shall be created by business requestors, GS projects by Procurement. Group Category Buyer is known to set up guided sourcing events.

However, how can we allow business requestors to create guided sourcing requests but not guided sourcing projects, when the group permission category buyer enables both?

Is it planned to restrict sourcing project templates? Or can permissions for business users steer the correct assignment?

Thanks in advance and KR

Accepted Solutions (0)

Answers (1)

Answers (1)

0 Kudos

Hello Katherina,

You are correct that restricting access through the sourcing project templates is the best way to go about this.

You can either restrict access by project group membership for Guided Sourcing events by setting global groups:

After enabling the CF-5318 - Limit Users by Global Groups feature, a template creator can specify the global groups or users allowed to be added by a user for any particular project group.

Please follow the steps below to enable this function, after creating your global groups, if required:

  1. From your dashboard, click Manage > Templates > Actions > Create
    • Or simply Open your existing template
  2. On the Team tab, click Actions > Edit Team Members
  3. Add or Edit a project group
  4. Set both Can owner edit this Project Group Restrict Additional Members? rules to Yes
  5. Click Select and add global groups to Permitted Groups list
  6. Click OK and Publish the template


Restrict who and when the template can be can selected when creating a Guided Sourcing project, by creating a condition on the Guided Sourcing template.

You can apply conditions to entire templates to control whether they are presented as a choice during project creation based on values users specify for other project attributes such as Commodities, Region, Supplier, and so forth. If you plan to use many templates for a project type, making them conditional can help users choose the correct templates for specific business processes. See Linking Conditions to Entire Templates [see page 93 of the Project Template Guide] for details.

You can associate a condition with an entire template by setting the Conditions field in the Properties area of the template. If you associate a condition with an entire template, the template appears as an option during project creation only if the field that makes the condition true is set appropriately.

  1. Define the condition you want to apply to the entire template as described in Defining Condition Expressions Using the Condition Editor [page 84] or Defining a Condition with User Responses to Questions [page 86 of the Project Template Guide]
  2. In the Properties area of the Overview tab of the template, select Actions > Edit Properties
  3. In the Conditions field, select the condition you defined earlier
  4. Select Save.
  5. Make sure the condition appears in the Overview tab of the template in the Conditions field.

To restrict this further from a Sourcing Request to a project make sure they are not an Admin or in the Project Owner group in the Request.

Admin permissions:

  • Contract Administrator
  • Commodity Manager
  • Customer Administrator
  • Event Administrator
  • Internal Contract Administrator
  • Limited Event Administrator
  • Project Administrator
  • Sales Contract Administrator
  • Sourcing Project Administrator

I hope this is all helpful to you to get started on setting this up.