TATER Ops
Help desk and task management on the same TATER ecosystem. Same identity, same database, same theme — different surface.
What it is
TATER Ops is a sister application to TATER Security. It lives at ops.tatersecurity.com and serves operational task tracking — IT requests, sales engagements, document reviews, scheduled recurring work. The TATER acronym for this product expands as Tasking, Assignment, Templating, Engagement & Reporting.
Signing in
Use the same Microsoft Entra ID account you use for TATER Security. Both apps share the same Entra app registration (45afb90d-…) and MSAL session — sign in once via login.html, both apps recognize you. Multi-tenant audience: accounts in tatersecurity.com and any other tenant where the app is registered work.
Navigation
- Workspace — Dashboard (default landing page), Tasks (full list with KPIs and filters), My Tasks (assigned to you)
- Configure — Task Catalog (reusable task definitions), Templates & Schedules (recurring auto-generated tasks)
- Knowledge — Policies, Documentation, TATERpedia (read-only browse views; create/edit deep-links to TATER Security)
- Reference — TATER Security ↗, Help & Docs ↗
- Administration (SuperAdmin only) — deep-links to TATER Manage
Tasks
Every task carries: title, description (Markdown), category (IT / Sales / Engagement / Proposal / Booking / Lead / DocumentReview / Other), priority (Critical / High / Normal / Low), status (Open / InProgress / OnHold / Closed / Cancelled), requester, contact, assignee, due date, and optional links to TATER Security entities.
Cross-product linkage
The most distinctive feature: every task can link to a specific TATER Security record. Click + Task in Ops on a control / risk / audit / vendor / policy / wiki / config-doc detail panel in TATER Security — Ops opens with the create-modal pre-filled with the linked entity. From the TATER side, the same panel shows 📋 N open tasks when there are linked tasks.
Comments
Every task has a comments thread powered by the same Comments API used by TATER controls. Comments are auditable, MCP-visible, and appear in the platform-wide Activity Log.
Task Catalog
Reusable task definitions for common requests (e.g. "New employee onboarding — IT setup"). Click any catalog entry from the Tasks page to open the create modal pre-filled with that catalog's defaults (category, priority, assignee, description). SuperAdmin / Admin can add and edit catalog entries; everyone can use them.
Templates & Schedules
Recurring task templates that auto-generate on a schedule. Cadences: daily, weekly (with day-of-week selector), monthly (with day-of-month). The cron job taskerTemplateScheduler runs at 06:00 UTC daily and generates tasks from active templates whose nextRunAt has passed.
Azure DevOps sync
When configured, TATER Ops tasks are mirrored to ADO as work items. Bi-directional:
- Outbound: every task create/update fires (fire-and-forget) to ADO. Status transitions are mapped (Open/InProgress → To Do, Closed/Cancelled → Done). The ADO work item ID is stored on the task as an external ref so subsequent updates target the same item.
- Inbound: configure an ADO Service Hook → POST to
https://api.tatersecurity.com/api/integrations/ado/webhookwith required headersx-tater-tenant-id,x-tater-organization-id, andx-tater-ado-secret. ADO state changes flow back to TATER Ops within seconds.
Configuration lives in TATER Manage → Connections → Azure DevOps Sync.
MCP integration
Three MCP tools work in both Claude Desktop and Microsoft 365 Copilot:
list_tasker_tasks— filter by status / category / assignedTocreate_tasker_task— Auditor+, supportslinkedTaterEntityType+linkedTaterEntityIdupdate_tasker_task— Auditor+, status / assignment / priority changes
Permissions
- Viewer — read tasks/catalog/templates
- Auditor — create + update tasks
- Admin — manage catalog and templates; soft-delete tasks
- SuperAdmin — full access including the Administration nav block (deep-links into TATER Manage)
Direct URL
Bookmark ops.tatersecurity.com. The app is also reachable at app.tatersecurity.com/ops.html. Either URL routes to the same SWA via the hostname-redirect script in TATER.html.
TATER