Introducing a Chrome extension
This has come up in three separate customer calls this month. We have a Zapier hack doing this today and it breaks weekly. We are working around it with a spreadsheet, which is no…
This has come up in three separate customer calls this month. We have a Zapier hack doing this today and it breaks weekly. We are working around it with a spreadsheet, which is not sustainable.
How it works
This blocks the quarterly report we send to the exec team. It would remove the last manual step before we can automate this.
- Enable vote weighting.
- Enable an RSS feed.
- Enable a public API rate-limit dashboard.
- Enable changelog email previews.
What changes
This blocks the quarterly report we send to the exec team. The current flow takes six clicks; it should take one. Even shipping it behind a flag would let us validate the approach.
- Enable granular email preferences.
- Enable SAML SSO.
- Enable attachment uploads.
- Enable board-level moderation.
How it works
Not urgent, but it would save everyone about an hour a week. Our ops team has a runbook step purely to work around it. We hit this every Monday during the weekly review.
- Enable multi-language content.
- Enable scheduled digests.
- Enable Slack notifications.
Limits
Our ops team has a runbook step purely to work around it. Even a read-only version would unblock us. Our support volume would drop noticeably if this shipped.
How it works
Even a read-only version would unblock us. Right now this costs us roughly two hours a week. Screenshots are attached in the thread below.
- Enable an RSS feed.
- Enable post templates.
- Enable webhook retries.
- widget
- accessibility