Ideas
Our approach to product feedback
The benefits of giving us your product feedback
What happens to your product feedback
Our product teams meet regularly to go through new requests. Once we have verified that a request isn’t already available in the system, we change the status to Accepting votes so that more people can vote, prioritize, and give us information. This allows us to gauge demand, gather use cases, and establish impact & value.
How we choose what to implement
- Customer feedback - there are many ways we listen for your feedback:
formal customer interviews and other research activities
events like Greenbyte Forum conferences and trade shows
comments and votes on issues in Greenbyte Influence - CSM team insights - our CSM team knows which issues are the most challenging and most common for customers.
- Product analytics - we track how users move through the system, which helps us understand how existing features are being used.
- Product strategy - our long-term strategic vision for the product.
Custom applications
-
Trainee Personnel qualification
Is it possible to add a "Trainee" section under personnel qualifications? There are many technicians who do not have any qualifications yet and it would be advantageous for OCC etc... to be confident on the status of the technician and know to not allow them to take control of a turbine and that only site access is allowed.
2 votesThanks for your feedback, this is a great request. It's open for voting from other users.
-
Single Sign On and external authentication
We utilise Microsoft SSO for our IDAM across all our SaaS platforms and Breeze should allow sign on with OAUTH.
This is now a security requirement for all our platforms, and considering Breeze taps into to Operational systems, its a key target for these requirements.
1 voteThanks for your feedback, this is a great request. It’s open for voting from other users.
-
User permissions: edition of existing alerts
I would like to provide a Limited user with access to the section Administrate->Alerts, but without permission to edit the existing alerts (similar to the permissions that exist for dashboards).
1 voteThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Be able to generate an audit trail of users switching work parties
Sometimes, technicians have to leave a work party on a turbine and work with another work party on a different turbine. If we add their name onto the new work party, there is no way in the future we can track the fact that he/she was working with another work party previously. Could we have a tracker that indicates which work parties a user has been associated with in a day?
6 votes -
User created content rights should be administrated not only by creator (Templates - Custom Dahsboards - etc.)
As currently implemented - user created content such as Report Templates - Custom Dashboards - etc. - can only be administrated (VIEW and EDIT rights) by the creator.
Problems:
team work limited
deleted users creates "zombie" Reports/Dashboards that cannot be administrated by anyone
Suggestions:Users of the Administrators group should always have access to these settings - everywhere
A third right could be added: VIEW/EDIT/ADMINISTRATE and distributed by creator/administrators among users5 votes
- Don't see your idea?