Skip to main content

The data screen

Where every part of a timetable is edited — the navigation down the left, what the topbar does, and how undo behaves.

The timetable view shows you the result. The data screen is where the ingredients live: teachers, subjects, rooms, groups, the lessons themselves, and the rules that constrain them.

Open it from the timetable with Data, or from the dashboard card.

The data sections, from days and hours through to sharing.
The data sections, from days and hours through to sharing.

The navigation

Everything is grouped down the left-hand side, and the order is deliberate — it mirrors the way the desktop FET application arranges the same data, so anyone who knows one can find their way around the other.

Resources comes first, because nothing else can exist without it. It starts with Days & Hours, the time skeleton every lesson is placed into, then the things a lesson is made of — teachers, subjects, activity tags, rooms, buildings, student groups — and ends with Activities, the lessons themselves.

Constraints holds the rules, split into time and space. Editors also get Pre-flight here, which checks the whole thing for contradictions before you export.

Configuration is the real-world context: the calendar the timetable runs in, and your institution profile.

Share & display collects the outward-facing surfaces — embeds, screens, announcements and access links.

Views is the way out to this timetable's other screens — the timetable grid itself, Insights, and Substitutions — plus the owner's activity log.

The number beside each section is a live count, and it updates as you work rather than waiting for a reload. Sections you have no permission to use are not shown at all, so the navigation is an honest picture of what you can do here.

The rail collapses to icons when you want the width back, and it remembers that choice.

The topbar

The timetable's name is a button. It opens the timetables manager, where you can switch to another one, rename, clone, merge another timetable into it, or delete — so moving between timetables never means going back to the dashboard first.

Beside it sits the mode badge, showing which FET solver mode this timetable uses. For the owner it is also the control that changes it; for everyone else it is a label. Changing mode is a significant operation and is covered in its own page.

Upload .fet and Download .fet are the round trip to the desktop application. The download runs a check first and will warn you — or, for problems FET itself would reject, stop you — before producing a file.

Timetable takes you back to the grid.

Undo

The two arrows in the topbar undo and redo your recent edits, and Ctrl+Z / Ctrl+Y do the same.

They cover the edits you make most often and most casually: changing a field on a teacher, subject, room or activity; bulk actions like activate, deactivate, lock, unlock and set weight; reordering or renaming days and hours; moving a student group to a different parent; turning a constraint on or off.

Some things are deliberately not undoable. Creating something, deleting something, removing a group from its last remaining parent, and splitting or combining activities all fall outside undo. These change what exists rather than what it says, and an undo that quietly recreated a record under a new identity would leave every reference to it pointing at nothing. Being told plainly that these are one-way is better than an undo that appears to work and does not.

For the same reason, history is cleared when you switch sections. Undo applies to the section you are working in, not to everything you did this afternoon.

If you need to reverse something that undo does not cover, that is what backups are for.

Who can edit what

The data screen is not all-or-nothing. Someone arriving through a share link sees only the sections their link permits, and write actions they lack are absent rather than present-and-failing. The owner sees everything, including the configuration and sharing groups, which never open to a share link at all.