Email
Password
Session valid for 12 hours · Contact admin to reset password
Signed in as —
My Weekly Schedule
Request Shift Change
Request Type
Date
New Start Time
New End Time
Reason
Apply for Leave
Start Date
End Date
Leave Type
Notes (optional)
Your leave request will be sent to admin for approval. It will appear in the team calendar only after approval.
My Requests
Leave Requests
No leave requests yet.
Shift Change Requests
No shift requests yet.
Team Leave Calendar
Dashboard
Auto-run: ON (30m)
No Reply >20min
0
Unanswered emails
Missing Ticket ID
0
No TKT# in reply
SLA Breaches
0
Commitment overdue
Missed Handover
0
Today's shifts
Recent Flags
No flags yet. Run the monitor to start.
Active Reminders
No active reminders
Monitor Log
No runs yet
All Active Flags
TimeSubjectSenderTypeResponsibleAction
No flags. Run monitor first.
SLA Reminders
How reminders are created:
◈ Auto-detected — When an SRE reply contains a time commitment phrase (e.g. "will update in 2 hours", "reply by 3PM", "will get back by EOD"), the system creates a reminder automatically with that deadline.
◈ Manual — Use + Add Manual when a commitment was made verbally or via a channel not covered by auto-detection.
◈ Overdue — A reminder turns red and raises an SLA Breach flag if the deadline passes with no further SRE reply in that thread.
◈ Dismissed — Dismiss a reminder once the commitment is fulfilled or no longer relevant. Dismissed reminders are removed from this view.
No reminders tracked.
Shift Roster Template
One continuous 8-hour block per member · Each member gets their own days of week (e.g. Mon–Fri or Tue–Sun) · Repeats every week indefinitely — only update when a new roster cycle is prepared or a member's shift changes · This is the base template; leaves override it per-date.
No shifts configured. Add members in Settings first.
Mail Monitoring Roster Template
Separate from shift roster · Within each member's 8-hour shift, assign a continuous mail monitoring window (2–6 hrs) · Only one member monitors at any time — no overlaps allowed · Repeats weekly same as shift roster · Must be within the member's shift hours · Monitor tracks this to identify who was responsible when a flag fires.
No monitoring slots configured.
Leave Register
Per-date leave overrides on top of the repeating roster · Types: Full Day, Half Day (1st/2nd half), Short Leave (first or last 2hrs of shift) · Backup for shift coverage and mail monitoring backup are both required before saving · Leaves appear as overlays on the Weekly Grid View.
MemberDateTypeShift BackupMonitor BackupNotes
No leaves logged
Leave Calendar
Full Day Half Day Short Leave
🏥 Leave Focused View
Auto-refresh: off
Leave Focused View
Opens in full-screen overlay — designed for LED/TV displays
Shows ±2 days before / 18 days forward from today (configurable in Settings). Each leave day gets a large cell with member names. Auto-refreshes from the database on the interval configured in Settings.
Pending Leave Requests
No pending leave requests.
Pending Shift Change Requests
No pending shift requests.
Weekly Grid View
Shift (per-member color)
✉ Mail Monitor
Leave
↩bk Backup
Rows = hours (00:00–23:00). Columns = days. Shows shift, monitoring windows, leaves and backups as overlays.
Outlook Connection
Authentication Method
Microsoft Graph Access Token
Get from Graph Explorer. Token expires — you'll need to refresh it periodically.
Shared Mailbox / User Email
Mail Folder ID or Name
For subfolders paste the folder id from Graph Explorer. For Inbox just type inbox.
Auto-run Interval
Monitor Rules
No-Reply Alert After (min)
Ticket ID Regex
Handover Subject Pattern
Thanks / Confirmation Keywords (last reply is acknowledgement — skip No-Reply & ticket flag)
If the last reply contains any of these, the thread is treated as acknowledged — no No-Reply flag, and ticket check is also skipped.
Resolution / Closure Keywords (last reply confirms issue is closed — skip ticket flag)
If any SRE reply contains these phrases, the thread is treated as closed. No ticket is required and No-Reply flag is suppressed. Add your team's common closure phrases here.
Lookback Window (hours)
Skip Senders — ignore entirely (no checks at all)
Threads where the original mail is from these addresses are skipped completely — no reply check, no ticket check, nothing.
Skip Ticket Check for these Senders (reply/no-reply checked, ticket not required)
If the original mail is from these addresses, reply will still be checked but no ticket ID will be required.
Skip No-Reply check — Subject Keywords (comma separated, contains match)
If subject contains any of these keywords the No-Reply flag is skipped entirely.
Skip Ticket check — Subject Keywords (comma separated, contains match)
If subject contains any of these keywords the Missing Ticket flag is skipped entirely.
SLA Phrases — Full Examples (add real phrases your team uses)
Add complete example phrases comma separated. Supports: X mins/hours/days, by 3PM, by EOD (counts as 10PM), shortly/soon/some time (counts as 2 hours), tomorrow EOD/3PM.
EOD Time (24hr format) (used for "by EOD" reminders)
Hour of day counted as End of Day. Default 22 = 10PM.
Learned Ticket Patterns
Patterns added automatically when you use the 📚 Teach button on a flagged mail. These are merged into the Ticket ID Regex above and persist across runs.
No patterns learned yet.
Team Members
Full Name
Email
Role
Password
No members yet
Projects
Configure projects with client names, emails and keywords. The monitor will automatically group matching emails under each project and generate AI summaries per topic on the Projects tab.
No projects yet.
MongoDB API Connection
Not connected
Connect to your Node.js/Express API backed by MongoDB Atlas. When connected, all settings, members, roster, and leave data are loaded from and saved to the database — shared across all users. Flags, run history, and debug logs remain local to this browser session.
API Base URL
API Key (X-API-Key)
Leave Focused View Settings
Auto-refresh interval
Days before today to show
Days after today to show
Demo Mode

No Outlook token configured? Simulate a full monitor run with synthetic email data to preview the portal.

Run History & Export
Run TimeEmails ScannedFlagsRemindersStatus
No history yet
Resolved Flags Archive
No resolved flags yet
Debug Log
Full decision log from the last monitor run. Copy or download and share with support to diagnose issues. Shows every thread processed, every exclusion decision, every handover check.
No debug log yet. Run the monitor first.
Connect JIRA
JIRA Domain
Just the domain — no https://
Your JIRA Email
How to get your API token:
1. Go to Atlassian API Tokens
2. Click Create API token
3. Give it a name e.g. SRE Monitor
4. Copy the token and paste it here

✓ Token never expires unless you revoke it
✓ Read-only access to your filters and tickets
✓ No admin approval needed
Project Intelligence
Mails are matched to projects by client email addresses or subject/body keywords. Summaries are generated per topic thread using AI. 🟡 Yellow = needs attention · 🔴 Red = critical / escalated · 🟢 Green = resolved / no action needed. Add projects in Settings → Projects or use the + Add Project button above.
No projects configured yet.
Go to Settings or click + Add Project above.