Publish once, apply everywhere
Fee structures, academic calendars, and grading rules are set centrally and published to every campus.
01 · Your network, not just your schools.
Workspaces & Governance
Network policy and school work stay clearly separated across campuses.
Hear it from Syfty
EdSyft module 01
Why it matters
The operating detail behind the promise.
A school group is not one school repeated many times. A trust running twelve campuses has one problem a single school never faces: knowing, without fifteen phone calls, whether Campus 4's fee policy actually matches what the board approved, or whether Campus 9 is still marking attendance on paper. Edsyft's answer is to give the organization and each school a genuinely separate workspace, not a shared screen with more or fewer buttons depending on who's logged in.
The organization's workspace is where policy is authored: the academic calendar, subjects, grading schemes, and fee structures are edited as a draft, then published. The moment a version is published, every school's workspace resolves the new configuration automatically. There is no step where someone re-enters the same calendar twelve times. Every setting carries a record of whether it came from the org or was overridden locally, so nobody has to guess why one campus's fee due-date looks different from the rest.
Not every capability is meant to be centralized, though, and Edsyft doesn't force one answer. For leads, admission documents, fee corrections, attendance policy, and exam setup, the organization chooses, campus by campus, whether that capability is org-locked, handed to the school to run directly, or hidden from that school's workspace entirely. A newly opened campus can stay locked down on everything until its office is trained; an established one can run its own fee corrections and document review without waiting on head office.
None of this relies on people remembering to stay in their lane. A school-scoped login simply cannot reach another campus's records. The boundary is enforced where the data lives, not just hidden by a menu. When the network needs a pause, such as an admissions freeze before a board meeting or a fee-collection hold during migration, the organization can pause admissions or fee collection across every campus in one action, with schools seeing the effective state as read-only until it's lifted.
What it handles
The work that should not disappear between screens.
Every capability below maps to a real operating decision, handoff, or record inside the module.
Delegate or lock, campus by campus
Decide what each school manages on its own and what stays with the network, module by module.
Isolated by design
A principal sees their campus. An org admin sees the network. Nothing crosses over by accident.
Which campus needs attention today
Unmarked attendance, pending admissions, fee delays, and unresolved approvals, in one view.
Where collections are getting stuck
Dues, concessions, refunds, and receipt gaps tracked before monthly pressure builds.
Which school is falling behind
Compare attendance marking, fee work, and admissions progress across every campus.
How it is controlled
Rules that make the workflow trustworthy.
Permissions, approvals, and state changes are part of the workflow itself, not instructions left for a staff meeting.
Delegation, per capability, per school
Leads, document review, fee corrections, attendance policy, and exam setup can each be set independently to org-locked, school-managed, or hidden, for each campus.
Copy a working setup across campuses
Once one school's delegation settings are right, apply the same set to another campus in a single action instead of rebuilding it.
Org-wide pause, one switch
Admissions or fee collection can be paused across every campus at once, schools see the effective state, they don't set it.
Value propositions
A better day for the people doing the work.
What changes for the team once this module is running in daily work.
Config, versioned like a release
The organization edits a draft, publishes it, and every school resolves its own effective version, with a field-level record of what came from the org and what a school overrode.
Org-wide pauses, in one action
Pause admissions or fee collection across every campus at once. Schools see the effective state, read-only.
Audit trail on sensitive changes
Who changed what, when, and from where is logged automatically, including denied attempts.