Ticku — Product Overview
Ticku is a Ticketing & Workflow Management System that runs both as a Microsoft Teams tab app (desktop and mobile) and as a standalone web application. It is delivered as a shared multi-tenant SaaS — one platform hosts many customer organizations, each fully isolated from the others.
Who is it for?
Teams that track support requests, consulting engagements, development work, and internal tasks — inside Microsoft 365 or a browser. Organizations self-register by their email domain and manage their own users, projects, and workflows.
Core Capabilities
| Capability | Description |
|---|---|
| Multi-tenant workspaces | One login, many organizations. Users can belong to several tenants and switch between them |
| Project types | Support, Consulting, Dev, and Epic project types — each with its own hierarchy, workflow, priorities, and roles |
| Subjects → Tickets → Sub-tasks | Work is organized into Subject folders, then tickets, then sub-tasks (naming varies by project type) |
| Kanban, list & grid | Multiple views per project, including a drag-and-drop board and a timeline/date-range view |
| Bulk upload | Excel-style paste grid to create Subjects, tickets, and sub-tasks in one go |
| Dynamic roles | Per-project roles built from a permission catalog, seeded per project type and editable by admins |
| SLA tracking | Priority-driven SLA for Support projects, honoring a configurable master calendar (working hours, weekends, holidays) |
| Escalation | Flag a ticket as escalated with an urgency reason and notify the right people |
| Time & work logging | Per-ticket time tracking (Consulting) plus a personal daily work log |
| Analytics | Dashboards across projects and tenants with charts for throughput, SLA, workload, and more |
| Custom attributes | Admin-defined per-project fields (text, select, date, cascading) |
| Email-to-ticket | Inbound email converted to tickets, with threaded replies and per-mailbox routing to projects |
| Comments & @mentions | Threaded discussion with replies, emoji reactions, and mention notifications |
| Followers | Subscribe anyone to a single ticket or sub-task without giving them the whole project |
| Notes, reminders & meeting logs | Lightweight personal and team productivity tools alongside tickets |
| Notifications | In-app, email, and Teams notifications with per-user preference levels |
Two Ways to Sign In
- Microsoft Teams — silent single sign-on via Teams; no password, no login page.
- Web browser — Microsoft (Azure) SSO, or email + password with OTP verification.
New organizations can register themselves at /register-organization; users then join automatically by email domain, or by invitation as a guest.
Deployment Model
Shared multi-tenant SaaS. A single deployment (app + PostgreSQL + Azure Blob) serves all tenants. Data is isolated per tenant by a tenantId column and an isolation layer that makes cross-tenant access impossible from application code — see Multi-Tenancy.
→ Continue to the Feature Matrix for what each role can do, or Licensing & Pricing for commercial terms.