We would like the project invite email notification to be manageable through Project Notification Settings. Our company supports multiple portfolio clients with many smaller projects. We have internal operations support team members who need to be added to every project by default. However, whenever a new project is created from a template, or when users are added manually, those team members receive an invite email notification. Because we often open 10–20 new projects per week, this creates excessive notifications and adds unnecessary noise for internal teams, customers, and suppliers. Current Behavior When users are added from a template, or the project members screen, the system automatically sends an invite email notification. There are currently ways to add members without an invite through certain project tool menus (example: Contracts), but this functionality is not available through the Project Members screen, which is the primary member management area. Business Impact High-volume project creation and member assignment generates repeated invite emails that: overwhelm internal teams who are added to every project cause customers to receive more notifications than necessary create confusion or frustration for suppliers receiving repeated invites increase the chance that important emails are missed due to “notification fatigue” Use Case Scenarios Operations team members added to every project Our Safety, Insurance, Finance, and Labor Compliance users need visibility on all projects for setup, administration, troubleshooting, reporting, and ongoing coordination and cannot be left waiting for access. No opt outs available There is no current opt out for our teams or our clients to manage the email notifiers they are receiving and can create perceived annoyance and ongoing frustrations while trying to maintain portfolio visibility. Bulk onboarding or transitions During onboarding or team member transitions, we may add a user to many projects they are newly joining. The invite emails create clutter and distract from real action-required notifications, and depending on the team members role could result in hundreds of notifications in the case of a new operations support team member. Adding members for recordkeeping rather than collaboration Sometimes external users are added to projects to support internal documentation, centralizing project contacts, optional project document access, or reporting purposes, not because they need to actively log in or participate. Sending an invite in these cases provides no value and contributes to unnecessary communication and confusion.
Show More