on 2023 Jul 03 11:11 PM
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
Request clarification before answering.
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:
OR
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.
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:
I hope this is all helpful to you to get started on setting this up.
Melissa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.