Notifications¶
Kiket provides a comprehensive notification system to keep you informed about important events across your projects. You can customize which events trigger notifications and through which channels they're delivered.
Notification Channels¶
Email Notifications¶
Email notifications are sent to your registered email address. You can configure:
- Frequency: Choose between immediate delivery or digest mode (hourly, daily, or weekly summaries)
- Per-event control: Enable or disable email for specific event types
Email notifications include direct links to the relevant issue or project, making it easy to take action.
In-App Notifications¶
In-app notifications appear in the notification bell icon in the top navigation bar. They provide:
- Real-time updates without leaving the application
- A notification center with history of recent notifications
- Quick actions to mark as read or navigate to the source
- Unread count badge for visibility
Slack Notifications¶
Integrate with Slack to receive notifications in your team's channels or as direct messages.
Setup: 1. Create an Incoming Webhook in your Slack workspace 2. Navigate to Settings → Notifications in Kiket 3. Enable Slack notifications and paste your webhook URL 4. Select which events should be sent to Slack
Slack messages are formatted with rich attachments including issue details, status, and action links.
Webhook Notifications¶
For custom integrations, you can configure a webhook endpoint to receive notification payloads.
Payload format:
{
"event_type": "issue_assigned",
"timestamp": "2026-01-03T15:30:00Z",
"user_id": 123,
"data": {
"issue_id": 456,
"issue_key": "PROJ-123",
"title": "Fix login bug",
"assigned_to": "jane@example.com"
}
}
Webhooks support custom endpoints and can be used to integrate with external systems, trigger automation workflows, or feed data into monitoring tools.
Push Notifications (Coming Soon)¶
Browser push notifications will allow you to receive alerts even when you're not actively using Kiket. This feature is currently in development.
Event Categories¶
Notifications are organized into categories for easier management:
Issues¶
| Event | Description |
|---|---|
| Issue assigned to you | When an issue is assigned to you |
| Issue status changed | When an issue you're watching changes status |
| New comment on your issue | When someone comments on an issue you created or are assigned to |
| You are mentioned in an issue | When someone @mentions you in an issue or comment |
Projects¶
| Event | Description |
|---|---|
| Project updates | Important project-level announcements |
| Milestone deadline approaching | When a milestone deadline is within the warning threshold |
| Sprint started | When a new sprint begins |
| Sprint completed | When a sprint is marked complete |
Team¶
| Event | Description |
|---|---|
| Team invitations | When you're invited to join an organization or project |
System¶
| Event | Description |
|---|---|
| Build failures | When a CI/CD build fails (if integrated) |
| System notifications | Platform announcements and maintenance notices |
| Weekly digest | Summary of activity across your projects |
| Daily summary | Daily recap of important events |
Billing & Usage¶
| Event | Description |
|---|---|
| Billing notifications | General billing-related updates |
| Usage quota alerts | When approaching or exceeding usage limits |
| Usage trend alerts | Significant changes in usage patterns |
| Usage projection alerts | Projections indicating potential overages |
| Payment failed | When a payment method fails |
| Subscription expiring | When your subscription is about to expire |
Integrations¶
| Event | Description |
|---|---|
| Extension alerts | Alerts from installed extensions (e.g., sync failures) |
AI & Insights¶
| Event | Description |
|---|---|
| Risk alerts | AI-detected project risks requiring attention |
| Developer Aide alerts | Suggestions from the AI development assistant |
| AI skill suggestions | Recommendations for skill development |
Approvals¶
| Event | Description |
|---|---|
| Approval requests | When an item requires your approval |
| Approval reminders | Reminders for pending approvals |
| Approval escalations | When an approval has been escalated |
| Executive approval alerts | High-priority approvals for executives |
Analytics¶
| Event | Description |
|---|---|
| Time tracking notifications | Updates related to time entries |
| Time tracking review digest | Summary of time entries requiring review |
Quiet Hours¶
Quiet hours allow you to mute non-urgent notifications during specific time periods, such as evenings or weekends.
Configuration: 1. Navigate to Settings → Notifications 2. Enable quiet hours 3. Set start and end times (e.g., 10:00 PM to 8:00 AM) 4. Optionally disable weekend notifications
Urgent events bypass quiet hours. Events marked as "urgent" (such as critical approval escalations or risk alerts) will still be delivered during quiet hours to ensure you don't miss time-sensitive items.
Configuring Notifications¶
Per-User Preferences¶
Each user can configure their own notification preferences:
- Click your avatar in the top-right corner
- Select Settings → Notifications
- Toggle channels on/off (Email, In-App, Slack, Webhook)
- Configure channel-specific settings (webhook URLs, email frequency)
- Enable/disable specific events for each channel
- Set quiet hours preferences
Best Practices¶
- Start with defaults: The default configuration is designed to balance staying informed without overwhelming you
- Use digests for low-priority events: Configure daily or weekly digests for informational notifications
- Set up quiet hours: Protect your personal time by enabling quiet hours
- Use Slack for team visibility: Route team-wide notifications to shared Slack channels
- Monitor urgent events: Keep email and push enabled for critical events that require immediate attention
Notification Audit Trail¶
All notification dispatches are logged for compliance and debugging purposes. The audit trail includes:
- Recipient and channel
- Delivery status (pending, delivered, failed)
- Timestamp and content hash
- Source event that triggered the notification
For organizations with blockchain audit trails enabled, notification dispatches are included in the cryptographic audit chain for tamper-proof verification.
API Access¶
Notifications can be managed programmatically via the REST API:
# List notifications
GET /api/v1/notifications
# Mark as read
PATCH /api/v1/notifications/:id/read
# Mark all as read
POST /api/v1/notifications/mark_all_read
# Get unread count
GET /api/v1/notifications/unread_count
See the REST API documentation for full details.