Examples of Access Control for Workflows

Here are some examples of access control for workflows.

Data Access Groups for Workflows

Here’s an example of how you can set up different teams in the US, so they function as data access groups based on their role, the types of change orders and attribute groups they manage, the actions they are responsible for, and other criteria.

• Team 1: Component Engineers who can create and manage Engineering Change Orders but only view Change Requests. They can manage all attributes except Change Cost extensible flexfield attributes.
• Team 2: Change Analysts who have permission to add and edit workflow approvers and participants, add affected objects, modify relationships, change status, and publish the workflow in the respective statuses. They can only see the workflow number for workflows in the CHIP Design Update, as they hold only the discover permission for this Workflow Type.
• Team 3: Suppliers who are U.S. based can add and edit the supplier comments of a problem report for which they are the suppliers, and the extensible flexfield attribute Location is set to US.
• Team 4: John and Sam are the Product Change Approvers, who only require viewing the Change Order Header .

Here's a table showing the configuration of teams

Team Name	Users and Filtered Lists	Permission	Condition	Access Groups
Team 1	Component Engineers	Create	Type = Engineering Change Order	Not Applicable
	Component Engineer	Manage	Type = Engineering Change Order	All attributes and Tabs
	Component Engineer	View	Type = Change Request	All attributes and Tabs
Team 2	Change Analysts	Manage	Type = Commercialization Change Order EFF. Compliance = Yes	Basic Attributes Affected Objects Workflow Activity Relationship
	Change Analysts	Change Status	Type = Commercialization Change Order EFF. Compliance = Yes	Not Applicable
	Change Analysts	Publish	Type = Commercialization Change Order EFF. Compliance = Yes	Not Applicable
	Change Analysts	Discover	Type = CHIP Design Update	Not Applicable
Team 3	US Suppliers	Manage	Muletiselect.EFF.Location= US	EFF.Supplier Comments
Team 4	John, Sam	View	Type = Engineering Change Order	Basic Attributes EFF.AG.ProductDesign data Affected Objects

Filtered Lists for User-Based Access

As an organization, you can create teams to maintain a hierarchy of permissions, enhancing security and efficiency in their SCM operations. For example, you can set up the following teams:

Team A: grants view-only access to all company users, ensuring visibility.

Team B: a more exclusive group, empowers top management, managers, component engineers, and product engineers to manage workflows.

Team C: tailored for product engineers, enabling them to create new workflows

Here's a table showing the configuration of teams

Team Name	Users and Filtered Lists	Permission	Condition	Access Groups
Team A	All Users	View	Type = Engineering Change Order Priority - Medium and High	Access To All attributes and Tabs
Team B	Manager Gorup Component Engineers Product Engineers	Manage	Type = Engineering Change Order Priority - Medium and High	Access To All attributes and Tabs
		Change Status	Type = Engineering Change Order Priority - Medium and High	Not Applicable
		Publish	Type = Engineering Change Order Priority - Medium and High	Not Applicable
Team C	Product Engineers	Create	Type = Engineering Change Order	Not Applicable