Playground, one app, or the whole suite?
PLAYGROUND is the demo. WORKSPACE embeds one app. SUITE — a shared calendar across many NIFI products.
Playground, one app, or the whole suite?
PLAYGROUND
0 see demo- checkMonth, week, day, list
- checkSample events, vi locale
- checkView-switch toolbar
- removeEmbed a real app
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.