New integrations are not active by default
Problem to solve
When setting up a new integration, the user needs to check the Active
checkbox in addition to entering other settings. This option is off by default, so it's possible for a user to enter all the appropriate settings for the integration but fail to check the Active
box, which can result in confusion.
Here's an example of this in action:
Further details
Make it easier to on-board those moving from GitHub to replicate workflows.
Proposal
Set the Active
checkbox state to "checked" the moment a value is entered into a field.
Frame 1 | Frame 2 |
---|---|
![]() |
![]() |
Documentation
Will require review of our project service docs pages to align with the implemented solution. For example, on the Slack Notifications Service docs, it specifically mentions Check the Active checkbox to turn on the service.
. If we set that checkbox to active by default, we could consider removing that.
Testing
Setting the first save as Active by default risks enabling unintended Slack notifications. However, users intending to have inactive notifications would likely be aware of the need. New users might not.
What does success look like, and how can we measure that?
It may be possible to track the efficacy of this with Snowplow data, however I think it's low-prio to dig in to this further. The following funnel should be reduced:
- User goes to a new integration that is currently unused
- User enters values, does not check
Active
, and saves the integration - Within a few minutes, user revisits page, checks active, and saves