We'd love to have the ability to ask users questions during reporting, and then have those responses made available to match against as rules. I envision it as a new model, ReportQuestion, with an ID, a value, and an order. Or it could be configured as part of the chrome extension, as part of the settings pushed out by the administrator. When the report button is clicked, we could have the user select e.g. whether they clicked any links, downloaded any files, or typed their password in anywhere. Based on that, we could automatically route the report to the appropriate team to react to the situation.
This would basically require three changes:
An update to the reporting UI in the extension to ask the questions (and to pass them along as part of the reporting JSON)
An update to the report endpoint to store those values
An update to the rules engine to allow us to match against the value of an admin-defined question when creating rules
We could go over the top with this, and build in an entire form builder, or we could just let the user specify HTML form fields on their own, and inject those into the popover when reporting, and have the report JSON include a "form" field that pulls in any named input in the popover and includes it. There are a lot of ways to go with this. For our use case right now, I think we've only wanted boolean responses, but I can imagine others wanting something else.
We'd love to have the ability to ask users questions during reporting, and then have those responses made available to match against as rules. I envision it as a new model, ReportQuestion, with an ID, a value, and an order. Or it could be configured as part of the chrome extension, as part of the settings pushed out by the administrator. When the report button is clicked, we could have the user select e.g. whether they clicked any links, downloaded any files, or typed their password in anywhere. Based on that, we could automatically route the report to the appropriate team to react to the situation.
This would basically require three changes:
We could go over the top with this, and build in an entire form builder, or we could just let the user specify HTML form fields on their own, and inject those into the popover when reporting, and have the report JSON include a "form" field that pulls in any named input in the popover and includes it. There are a lot of ways to go with this. For our use case right now, I think we've only wanted boolean responses, but I can imagine others wanting something else.
Is this something you'd be interested in adding?