Zyntra OS
Zyntra Legal
Zyntra Real Estate
Zyntra Hotel
Zyntra E-commerce
Zyntra Appointments
Zyntra Repair
Zyntra Garage
Zyntra Concierge
Zyntra Contracting
Zyntra Clinic
Zyntra Dental
Zyntra School
Zyntra University
Zyntra Call Center
Zyntra OTAZyntra OS features
Projects your customers can follow, and hours that become invoices
From a classic plan to agile sprints, every project keeps its tasks, milestones, time and money together — and one rule for overload is shared by tasks, sprints and the workload screen.
What sets Zyntra OS projects apart
Four things a person running projects sees here every day.
Every project knows if it makes money
«Did this project make us money?» — answered while the project still runs, not after it closes.
- Revenue: every invoice raised on the project
- Labour cost: every hour logged on its tasks, at the hourly cost kept on that timer
- Direct expenses: its expenses, without the voided ones
- Net profit and the margin, live, in the project’s own currency — a figure in another currency is counted aside, never mixed in
- No spreadsheet beside it: the figures come from the invoices, timers and expenses your team already enters, and only people whose role may see money see them
You see a project at risk before it is late
A budget can run out before the deadline does; the warning comes while the work can still be re-planned.
- Health, the rule: a project under way with a budget is At risk when the share of its budget spent on expenses is higher than the share of its work done
- Work done is counted from its finished tasks, or set by hand; expenses in another currency are counted aside
- Flowrica tells you on the project — «… has spent 36% of its budget against 18% of its work done» — and says when a project passed its deadline and is not closed
- The Projects overview counts every project at risk, and each one opens from there
- The percentage spent is said only to people who may see money; everyone who reads the project sees At risk
Flowrica makes the project from one description
You describe the project once, the way you would tell a colleague; the plan is drafted for you to check.
- She speaks your language — Arabic too
- She reads the customer, the start and the deadline — even «next Sunday» or «end of December» — the budget and how it is billed
- She finds your past similar projects and drafts the milestones and tasks from them
- She asks only what your text did not say, with her suggestion already chosen — the project manager from the people who have room
- The hours each role needs, against the free hours of the people who can do it; if the plan ends after your deadline, she offers to add a person or move the date
- Nothing is made until you press Create; then a green card with Undo for one minute
Epics two ways, and sprints Flowrica fills
A small team wants a label on a task; a larger one wants epics, stories and tasks. Each project chooses.
- Epic labels on tasks, or Epics → Stories → Tasks — chosen per project, and switched later without losing a row
- A tree and a board: every bar is counted from the tasks inside it, with their story points
- Tasks grouped by epic or story, and «Epic › Story» on each row of the sprint backlog
- A new sprint: Flowrica ticks the tasks it could take — left over, overdue, due in its dates, high priority — each with its reason; you Add, with Undo for a minute
Connected to the tools your team already uses
Each one works with your own account. Jira, the Git hosts and the meeting services start in test mode: nothing is sent until you switch it off.
Jira
Choose a Jira project, map every status, priority and issue type to yours, match the people by email, and import. From then on both stay in step: your change goes to Jira when you save; Jira’s change comes back by Jira’s own call, or every few minutes (5 by default), and «Sync now» is always there. On a linked task, «Sync to Jira» sends a status and the one comment you write for it — every other comment stays inside.
You set up: a Jira email and an API token (on Server: a username and a password or personal token). No app to install.
GitHub, GitLab and Bitbucket
A commit or pull request that names a task («T-123») appears on that task, live, as the host sends it; a pull request’s state and its checks stay up to date, and a merged one can close its task. Several hosts at once.
You set up: an account, a personal access token (Bitbucket: an app password) and a webhook secret you choose; every call is checked against it.
Google Calendar and Outlook
Each person who asks syncs their own calendar both ways: their events come in, their own events go out. Nobody’s calendar is read who did not ask. The sync never sends an invitation and never deletes — a removed event is marked cancelled.
You set up: each person presses «Sync my Outlook calendar», or «Connect with Google».
Slack and Telegram
Six moments become one short sentence in your company’s language, with a link to the record: a task done, a new lead, a new customer, an invoice issued, an invoice paid and a ticket opened. Sent after the save, with retries.
You set up: a Slack incoming-webhook address, or a Telegram bot and chat. Off until you switch them on.
Meetings
A meeting on a calendar event, in Microsoft Teams, Zoom or Google Meet, or held inside Zyntra OS in the browser. The join link stays on the event and goes to the synced calendar with it.
You set up: Teams with the organiser’s own Microsoft sign-in, Zoom with your company’s own Zoom app, Google Meet with the organiser’s Google account.
Outgoing webhooks
The same six moments, sent to the addresses you switch on — Zapier, Make or your own — signed with your company’s secret, sent after the save so nobody waits, and retried.
Every ready connectionProjects, Tasks & Workload
Projects & Tasks
Every project with its tasks, milestones, time and money.
- Projects from templates, with statuses and priorities you name
- A Gantt chart with milestones and dependencies: dragging a task first shows what moves with it, and loops are refused
- Sprints with capacity, burndown, velocity, limits on work in progress, rollover — and “invoice the sprint”
- Timers on tasks become invoice lines, and an hour is billed once
- An alert when hours reach 85% of the estimate, and each project’s profit and loss
- A client project portal with sign-off; what the client sees is chosen per project
- Commits and pull requests from GitHub, GitLab or Bitbucket, and Jira issues, linked to tasks
- A weekly report for each customer’s project, drafted every Thursday in your mailbox — it leaves only when you press Send
Staff Workload
Who has too much on their plate, and who has room.
- Each person’s week against their capacity, day by day — one overload rule shared with Tasks and Sprints
- Suggestions for who can take a task over
- A performance page per person: on-time work, overdue work and attendance
- Staff shifting, holidays, a timeline, a kanban and a chart of the load
Dashboard and calendar
The company at a glance, and each person’s own day.
- An overview of sales, money and work, and My Space: each person’s tasks, reminders and calendar
- One calendar with tasks, projects, sprints, reminders and events as layers
- Each person’s calendar synced both ways with Outlook or Google Calendar; nothing is sent to attendees by the sync
- Meetings in Microsoft Teams, Zoom or Google Meet, or held inside Zyntra OS in the browser
Also in Projects
Who sees the whole project
A super administrator names the people who see all of a project — its sprints and every task — beyond what their own role opens. They read; writing still needs their own rights. A name taken away stays on the project’s trail.
Every hour counted once
Time a person logs is checked against their other time on any task, so the same hour is never logged twice; each task’s Timesheet ends with its total time.
Zyntra OS projects and workload
Does Zyntra OS have project management with Gantt charts and sprints?
Yes. A Gantt chart with milestones and dependencies, sprints with capacity, burndown and velocity, timers on tasks that become invoice lines, and a portal where the customer follows the project and signs it off. Projects, Tasks & Workload.
Can Zyntra OS show who is overloaded?
Yes. The Workload screen sets each person’s week against their capacity, day by day, with one overload rule shared by tasks and sprints, and suggests who can take a task over. Projects, Tasks & Workload.
Does Zyntra OS show the profit or loss of each project?
Yes. Each project shows its revenue (every invoice raised on it), its labour cost (every hour logged on its tasks at the hourly cost kept on that timer) and its direct expenses, then the net profit and the margin, live, in the project’s own currency. Only people whose role may see money see these figures.
How does Zyntra OS know a project is at risk?
A project under way with a budget is At risk when the share of its budget spent on expenses is higher than the share of its work done, counted from its finished tasks or set by hand. Flowrica says it on the project, and the Projects overview counts every project at risk.
Can Flowrica create a project from a description?
Yes. Write the project the way you would tell a colleague — she speaks your language, Arabic too. Flowrica reads the customer, the dates, the budget and the billing, finds your past similar projects, asks only what is missing, and drafts the milestones, tasks and the team it needs. Nothing is made until you press Create, and Undo is there for one minute.
Does Zyntra OS support epics and stories?
Yes, two ways, chosen per project: epic labels on tasks, or Epics → Stories → Tasks with a tree and a board where every bar is counted from the tasks inside it. A project can switch later without losing a row, and a new sprint opens with Flowrica’s suggested tasks, each with its reason.
How to use it, step by step
Every topic of the user guide for this part of Zyntra OS, with pictures of the real screens.
See it with your own work
Ask for a demo and our team will show you this part of Zyntra OS, in your language — Arabic too.