Is your team hitting these problems?
Every app has a different calendar
Booking, shifts, meetings and tasks do not share one UI. Teams relearn month / week / day on each product.
Resources get double-booked
Meeting rooms, cars and restaurant tables collide because calendars live in Excel, chat and separate apps.
You cannot see who is free before you assign
Shifts, leave and meetings are not on one grid. You only notice the shortage after you assign.
Drag-and-drop does not lock the past
Past events get edited by mistake. No lock per event or per resource.
Locale and timezone drift
Vietnamese calendar, week starts Monday, shift hours — each app rewrites it.
No audit of who changed the calendar
Who moved a meeting, cancelled a booking, changed a shift — not the same log as the NIFI workspace.
Month, week, day — same events, no lost context
- Switch month / week / day / list on one toolbar
- Events, rooms and people stay when you change scale
- Drag, resize, lock past events and lock by field
- Locale, week start, shift hours — not rewritten per app
- Playground so dev/design try the view before embedding
- Same identity, role and tenant as the NIFI workspace
Event types
One calendar UI for all operations calendars
Month view
A month grid for occupancy, events and coverage. Meeting / booking / shift chips on each day.
Week view
Hour bands by day. Shifts, bookings and meetings on one strip — change week without losing filters.
Day & agenda
Hour-level detail for the desk, dispatch and shifts. List view when you need print or audit.
Events & drag-and-drop
Create, move, assign. Lock move / resize / resource. Block edits to past events.
Resource booking
Rooms, cars, tables — block double-book on the same grid as people.
Team free/busy
Who is free, who is on shift, thin coverage — before you book a meeting or shift.
Playground
Try month / week / day with sample data before you attach a real app.
Embed in every NIFI app
Same nifiUI. Not a standalone calendar app, not a calendar silo.
Book rooms, cars and tables on one grid
Resources are rows. Days or hours are columns. Double-book is blocked before save — not after it hits operations.
Attach an event to people and resources at once. Front desk, dispatch and F&B see the same availability.
See who is free before you assign a shift or meeting
Free/busy, shifts, leave and meetings in one view. Finding out you are short after you assign — that pattern ends.
Same data as niTeam (shifts, attendance) and niTask (deadlines) — no calendar silo.
From people who write calendars to people who roster every day
Calendar dev / design
Month / week / day playground, locale, lock and resource rows — try before you embed.
PlaygroundFront desk / booking
Book rooms, tables and cars on a calendar shared with the map and folio — no parallel Excel.
Front officeHR / rostering
Shifts, leave, coverage. Team free/busy before you lock a shift on niTeam.
HRMDispatch / operations
Cars, meeting rooms, equipment. Block calendar clashes on niGo and niTask.
DispatchSales / guest care
Guest meetings, demos, follow-up on the same calendar as CRM — not a personal calendar off to the side.
CRMWorkspace owner
One calendar UI, one identity, calendar-change audit by NIFI role and tenant.
WorkspaceOne calendar, many apps — no silo
Each product does not draw its own calendar. CaliNi is the reusable calendar UI layer on NIFI ERP.niTel
PMSRate calendar, booking and room maintenance share the same calendar UI as the front desk.
niTeam
HRMShifts, attendance, leave — availability shows on CaliNi.
niTask
Dự ánDeadlines and milestones on week / day, no separate project calendar.
niUp
CRMGuest meetings, demos, follow-up attached to the profile — same workspace.
niGo
XeCar and driver calendars are resource rows, trips cannot overlap.
niPOS
F&BTable booking by time slot on the same calendar UI.
Lexfi
Hợp đồngSign and renew dates — events on the legal calendar.
nifiUI
Design systemCaliNi lives in nifiUI: shared theme, overlay and locale.
Frequently asked questions
What teams ask before embedding a calendar — views, resources, availability and where CaliNi sits in the suite.
- Pick a viewMonth, week or day — playground with sample data.
- Attach resourcesRooms, cars, tables, people on one grid.
- Embed the appTurn on CaliNi on a running NIFI app in niHub.
No. CaliNi is a calendar UI library (month / week / day / playground) embedded in NIFI apps. Sign in once from nifi.us or calini.nifi.us — same workspace, no calendar silo.
Yes. Same events, rooms and people when you change scale. List / agenda when you need print or audit. Playground to try a view before you attach a real app.
Rooms, cars, tables and equipment on the same grid as people. Double-book is blocked before save. Lock by resource when an event must not move.
From shifts, leave and meetings on the workspace — same data as niTeam and apps that already embed CaliNi. Not a parallel Excel file.
CaliNi does not replace a personal calendar. It is the operations calendar UI inside NIFI. External calendar sync is a per-workspace implementation, not default on the landing.
Playground demo is free. WORKSPACE and SUITE follow workspace size, number of embedded apps and implementation. Subscribe only to what you actually embed.
When embedded in an offline-first NIFI app (for example niTel), the calendar view travels with that app's local data. CaliNi is not a separate cloud calendar service.
Role and tenant follow the NIFI workspace. If you do not see the menu: ask an admin to enable the app in niHub. Past events and locked fields cannot be dragged.