Welcome to SmarterWX Collaborate Ideas, an interactive forum where SmarterWX users can suggest, discuss, and vote on product enhancement ideas. Feedback is a big part of how we work to improve SmarterWX. Your suggestions help us decide what improvements we make and which new features to investigate further.
We have had a high turnover of Project Managers requiring a high level of maintenance of our host data causing delays to our upload which is detrimental to the Collaboration process. It would be ideal for us to be able to select project and provide an alternate email address for the project during the upload process, similar to when you remove a user the projects get an updated email giving time before next upload to correct the data. in the attached, the users have left Sydney Water, but their projects have not yet been updated and rather than waiting for weekly updates to run it would be better to solve on the fly during the upload process.
To further clarify we would like to be able to have the option of which email address to add either a specific or tick a box for administration email.
Understood. I suppose the Admin email address could be used in the interim until the PM responsibilities have been handed over. Also please note some subscribers choose to adopt Single Sign-On to secure access to the platform which means when someone leaves they automatically lose access to SmarterWX.
When a project manager leaves it may take a few weeks to hand the project over to someone new. We have set-up an Admin email address managed by the administrators so that any communications will be received by a valid email address. It is important we disable exiting PMs as soon as they leave so they no longer have access to the system. We would then seek to fix the PM before next load.
Hi Stuart, thanks for sharing your idea. We can definitely look at providing an option (either as part of settings, or within the data upload flow) to specify a default value to be used if there is an issue with an email address. Are you suggesting that errors such as this are not rectified and retried until the next weekly update?