Channel Organization
Organize events into channels like signups, payments, and deployments. Familiar navigation that works like Slack.
Different teams care about different events
Marketing wants to see signups and conversions. Developers want to see deployments and errors. Founders want to see everything, but with some structure. A single stream of undifferentiated events serves none of these needs well.
Without organization, finding a specific event means scrolling through everything else. Understanding patterns means mentally filtering noise. Configuring notifications means all or nothing.
Quicklog channels solve this by grouping events into logical categories that your whole team already understands.
Channels work like you expect
If you have used Slack, you already know how channels work. Each channel is a named container for a specific type of event. Signups go to the signups channel. Payments go to the payments channel. When you send an event, you specify which channel it belongs to.
Channels appear in your sidebar navigation, just like Slack. Click a channel to see only those events. Switch channels to change context. Everyone on your team sees the same channels, but they can choose which ones to focus on.
Each channel can have its own icon for quick visual recognition. When scanning your timeline, you can tell at a glance whether you are looking at a signup, a payment, or an error.
Notification settings are per-channel. Marketing can get instant alerts for signups while developers get daily digests for deployments. Same workspace, different focus.
What you get
- Unlimited channels per project to organize however you need
- Slack-like navigation with channels in your sidebar
- Custom icons for quick visual identification
- Per-channel notifications with independent settings
- Filtered views to focus on one event type at a time
- Channel archiving to hide old channels without losing data
Common channel setups
SaaS product
Start with signups, payments, cancellations, and errors. Add upgrades and feature-usage as you grow. Marketing focuses on the first three, developers on the last two.
Developer tools
Add deployments for CI/CD events, webhooks for debugging integrations, and api-errors for tracking issues. Keep technical events separate from business metrics.
Launch campaigns
Create a waitlist channel for pre-launch signups. Add a conversions channel when you launch. Archive the waitlist channel afterward but keep the data for analysis.
Organize your events
Create channels that match how your team thinks. Add more as you grow.