School

The School module is one of the most important configuration modules in InstiKit. Every educational institution that uses InstiKit must have at least one school configured.

A school represents an individual branch or campus within your organization. Each branch maintains its own configuration, users, academic data, and operational settings while still being able to share information with other branches when required.

Note

The School module is designed for organizations that operate multiple branches or campuses which share data with each other. If your institution has only one campus, simply create one school and continue using InstiKit normally.

Multiple Branches

InstiKit supports managing multiple branches of the same educational organization from a single installation.

Examples include:

• ABC Public School, Main Campus
• ABC Public School, City Branch
• ABC Public School, East Campus

All branches can work independently while still sharing selected information across the system.

This feature is useful for:

• School groups
• Colleges with multiple campuses
• Coaching institutes with several centers
• Educational trusts operating multiple institutions

When Should You Use Multiple Branches?

Use multiple schools when:

• Branches belong to the same organization.
• Staff may work across branches.
• Students or employees may transfer between branches.
• You want centralized administration.
• Some data needs to be shared between branches.

Do not create multiple schools for completely independent institutions that have no relationship with each other. In such cases, use separate InstiKit installations instead.

Organization Association

Each school can optionally be linked to an Organization.

Example:

Organizations help group multiple schools under the same governing body while allowing each school to operate independently.

School Details

Every school maintains its own basic information.

Typical information includes:

• School Name
• Short Name
• Organization
• Assigned Administrators
• Creation Date
• Last Updated Date

From the School Detail page, administrators can also perform branch synchronization and configuration import operations.

Branch Synchronization

InstiKit allows one branch to synchronize roles and permissions from another branch.

This is especially useful when opening a new campus that should use the same security structure as an existing branch.

You can choose to synchronize:

• Roles
• Permissions
• Both roles and permissions

Synchronization helps maintain consistency across all branches without manually recreating every role.

Import Configuration

Administrators can import selected configuration data from another branch.

Instead of configuring every branch manually, you can copy supported configuration modules from an existing school.

This reduces setup time and helps maintain consistency across multiple campuses.

School Configuration

Every school has its own configuration and branding.

Configuration is maintained independently for each branch.

Examples include:

Assets

• School Logo
• Application Icon
• ID Card Signatures

School Information

• School Name
• Motto
• Accreditation Body
• Affiliation Body

Address

• Building
• Street
• City
• State
• Country
• Postal Code

Contact Information

• Email Address
• Phone Number
• Fax Number
• Website

Identifiers

Custom identifiers such as:

• Registration Number
• Board Code
• School Code
• UDISE Code
• Custom Labels

Incharge Details

Store important contacts such as:

• Principal
• Vice Principal
• Director
• Administrator
• Coordinator

These details can be used throughout the application, reports, certificates, and public pages.

Roles

Every school maintains its own set of user roles.

Roles define what users are allowed to access within that particular branch.

InstiKit provides several predefined roles to help administrators get started quickly.

Default roles include:

• Admin
• Observer
• Manager
• Principal
• Staff
• Accountant
• Librarian
• Exam Incharge
• Transport Incharge
• Inventory Incharge
• Mess Incharge
• Hostel Incharge
• Attendance Assistant
• Receptionist
• Student
• Guardian
• User

Administrators can create additional custom roles whenever required.

Note

The User role is generally reserved for users created through the Registration module. Since online registration is not commonly enabled for most schools, this role is rarely assigned manually.

Role Permissions

Permissions determine what each role is allowed to perform within the application.

Permissions are assigned role-wise using a simple permission matrix.

Administrators can:

• Filter one or more roles
• Filter permission groups
• Search permissions
• Assign permissions using checkboxes
• Remove permissions by clearing checkboxes

Changes take effect immediately for users assigned to those roles.

This approach makes it easy to manage hundreds or even thousands of permissions efficiently.

User-wise Permissions

Sometimes a single user requires permissions that differ from others assigned to the same role.

InstiKit supports assigning permissions directly to individual users.

Administrators can:

• Select a user.
• Select one or more permissions.
• Assign additional permissions.
• Revoke existing permissions.

User-wise permissions are useful when granting temporary or exceptional access without creating another role.

Example:

A teacher normally cannot edit fee records, but for a short period the administrator may grant that permission directly to the teacher instead of creating a new role.

Best Practices

For most schools, the recommended workflow is:

1. Create the organization (optional).
2. Create one or more schools.
3. Configure school branding and information.
4. Review or create user roles.
5. Assign role permissions.
6. Create users and assign roles.
7. Use user-wise permissions only when exceptional access is required.
8. Synchronize roles and permissions when adding new branches.

Frequently Asked Questions

Can I manage multiple branches from one installation?

Yes. InstiKit supports multiple schools within the same installation, allowing branches to share selected data while maintaining independent operations.

Does each branch have its own configuration?

Yes. Every school maintains its own branding, contact information, assets, roles, permissions, and configuration.

Can different branches have different roles?

Yes. Roles are managed independently for each school.

Can I copy roles to another branch?

Yes. InstiKit provides synchronization tools for copying roles and permissions between schools.

When should I use User-wise Permissions?

Only when an individual user requires permissions that differ from the standard permissions assigned through their role.

Related Documentation

• Organization
• Users
• Roles
• Permissions
• User Menu