Administration and Master Data workflow
Try this experience Staff registration
Register teachers and other staff once. Salary is entered later in Payroll.
Staff registration in LiveSchools365 Administration and Master Data
Staff registration is a Administration and Master Data workflow in the Platform foundation area of LiveSchools365 school management software. Register teachers and other staff once. Salary is entered later in Payroll. Schools use it so Consistent campuses, classes, subjects, staff, products, and institutional identity.
Maintain the school structure and lookup records that every workflow depends on. The people who typically work here are Super administrator, Administrator. The rest of the module stays one click away, so an inquiry, register, invoice, or stock movement does not have to be re-typed into another product.
What this workflow changes
- Connected staff identity This sits inside Administration and Master Data rather than a separate spreadsheet, which keeps the audit trail on the same student, staff, or item record.
- Designation from Staff Designations This sits inside Administration and Master Data rather than a separate spreadsheet, which keeps the audit trail on the same student, staff, or item record.
- Salary is set on Salary Definition This sits inside Administration and Master Data rather than a separate spreadsheet, which keeps the audit trail on the same student, staff, or item record.
How it fits the rest of Administration and Master Data
Open these related Administration and Master Data guides when you want the step before or after Staff registration:
- Master Data — Manage authoritative operational lookup registers.
- School settings — Maintain branding, numbering, and core institution configuration.
How schools evaluate this screen
During a demonstration or trial, Super administrator, Administrator should complete one realistic example: a new inquiry, a section register, a fee receipt, a notice, or a stock issue, depending on the module. Then confirm that the same record appears on the dashboard, the related report, and the next workflow. That is the test of a school ERP: one operational picture instead of parallel files.
Trend Developers can walk this exact screen against your admission, attendance, exam, or fee process. You can also start a 14-day trial and use the matching live form after sign-in.
All Administration and Master Data workflows · Start a trial · View pricing · Request a demonstration
Guide depth
Interface
Fields, controls, and effects
Use this reference to understand what each area accepts and what it changes.
Staff code / nameText · Input
- Purpose
- Enter the staff identity.
- Rules
- Staff code is required and unique.
- Application effect
- Creates Person and Staff identity.
Email / registered mobileEmail and phone · Input
- Purpose
- Set official contact channels.
- Rules
- Email must be unique when supplied; mobile should be provider-ready.
- Application effect
- Supports login and secure notifications.
Campus / designationSelects · Input
- Purpose
- Assign campus and a designation from Staff Designations.
- Rules
- Teachers set subject area and availability on Faculty and Timings. Other designations ask for the detail that belongs to that role.
- Application effect
- Stores the staff assignment.
Join date / employment statusDate and select · Input
- Purpose
- Record employment lifecycle.
- Rules
- Use current HR status.
- Application effect
- Supports active staffing reports.
Salary mode / base salarySelect and number · Input
- Purpose
- Set payroll basis.
- Rules
- Salary cannot be negative.
- Application effect
- Feeds payroll calculations.
Active recordToggle · Input
- Purpose
- Allow academic assignment.
- Rules
- Deactivate rather than deleting history.
- Application effect
- Controls timetable and allocation choices.