Administration
Switching modules, roles per menu item, code lists, campuses and languages.
Who it is for
Wise Ed runs in the browser, beside the school’s Wise Timetable, with nothing to install on the office’s computers. The school’s administrator decides which modules are on, who sees which screen, which systems may read and write through the API, and what personal data may leave. Every change is on record, and the school’s data comes out in one file whenever it wants.
The platform pages, and the modules IT is asked about first.
Switching modules, roles per menu item, code lists, campuses and languages.
Public API, Zapier, webhooks, Moodle and LTI, Microsoft sign-in, accounting.
Roles, logs, consents, what never leaves Wise Ed, and the full export.
Moodle sync and LTI 1.3 for Moodle, Canvas, Brightspace and Blackboard.
Several sites in one school: students, programmes, documents and rights per campus.
Import from files with a dry run and undo, export from every list, and the full export.
No. Wise Ed is a web application at the school’s own address under wise-tt.com, beside its Wise Timetable; the office, lecturers and students need only a browser.
Until roles are switched on, only the people on the configAdmin list see API keys. Once roles are on, the configAdmin people may give that screen to a role like any other.
Yes. A module switched off is hidden from everybody and deletes nothing; switched on again, everything is back as it was.
Book an online presentation. We will walk through how your student office works today and show you the same job in Wise Ed — with your programmes, not a demonstration dataset.