Component Members
The Members section allows you to assign team members to a component, promoting clear accountability, enhancing visibility, and fostering seamless collaboration. Assign sourcing buyers, product developers, and procurement coordinators here so responsibility for the material is explicit across the supply base.
By assigning members, you can clearly define who is responsible for or contributing to a specific component. This may include designers, product developers, sourcing staff, or quality assurance personnel. Member assignments support notification workflows and provide managers with a quick overview of workload distribution across the team.
Core Actions
These actions are available to all users with access to the component record and allow for basic member management.
| Feature | Description |
|---|---|
| Add a Member | Click the plus (+) icon on the component record to open the member menu. Use the search bar to find users by name and select the checkbox to assign them. |
| Remove a Member | Click the trash icon next to a member's name. A confirmation pop-up will appear to finalise the removal. |
Member Management
These features help you leverage member assignments for notifications and workload visibility.
| Feature | Description |
|---|---|
| Notification Integration | Member assignments can be linked to system notifications. When a component's status changes, only the assigned members receive an alert. This keeps communication relevant and reduces unnecessary noise for the rest of the team. |
| Workload Overview | Use member assignments to get a quick overview of who is working on what. This can help managers balance workloads, identify potential bottlenecks, and reassign tasks as needed to keep projects on track. |
Important Notes When Using Members
Removal Confirmation: Removing a member triggers a confirmation pop-up. Once confirmed, the removal is final and the member will no longer receive component-related notifications.
Permission Scope: The ability to add or remove members may depend on your user role and permissions. Ensure you have the appropriate access before making changes.
Best Practices
Assign Key Stakeholders Early: Add designers, developers, and QA personnel as members at the start of a component's lifecycle so they receive relevant notifications and stay informed throughout the process.
Review Workload Regularly: Use the member view to periodically check workload distribution across your team. Reassign components as needed to balance capacity and avoid bottlenecks.