Worker Overview
Manual refresh, no background polling
Total Workers
—
Owned by this Sub Admin
Active
—
Seen within 15 minutes
Idle / Pending
—
Idle over 15 minutes or profile pending
Proxy Faulty
—
Open worker issues
Resolved Today
—
Marked resolved
Supabase Egress Guard
—
NORMAL
Measures API response-body bytes. Warning at 400 KB, compact mode at 500 KB, hard protection at 600 KB body usage or 350 responses to preserve margin below 1 MB.
Workers
Workers create their own account at https://rmcwork.nestek.online. Test Key, Username and Password are entered here by Sub Admin.
| Name | Account Name | Account Email | Account IP | Location | Test Key | Username | Password | Status | Proxy | Last Seen | Action |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Open Workers to load records. | |||||||||||
Proxy Faults
Worker-reported proxy issues
| Worker | Fault Description | Reported | Status | Resolved | Action |
|---|
Activity
Important events only, refreshes are not logged
| Event | Detail | Worker ID | Time |
|---|
Settings
Independent RMC Sub Admin profile
Sub Admin accounts are provisioned independently in Supabase Auth, then linked once to
rmc_sub_admins. Workers use their own RMC Worker accounts. Worker login passwords are managed by Supabase Auth and are not shown here.Push notifications are device-specific. Use the bell in the top bar to enable or disable push on this device. Foreground worker alerts also play the local RMC beep after the first user interaction unlocks browser audio.