Frequently asked questions

No. Institutions take the modules that address their current problem and add others later. Which modules are included is set out in your proposal; nothing on this site should be read as meaning every module is part of every deployment.

Admissions; academics and student administration, including electives, examinations, grading and transcripts; fees and finance; HR and payroll; institutional operations such as stores, hostel and transport; and placement and executive education. Each area is described on its own solution page.

Much of what varies between institutions is configuration that your own staff control: the admission form, scoring criteria, fee structures, grade scales and curves, elective rules and feedback forms. Where a regulation needs something the standard modules do not do, we assess it as customised development and say so in the proposal.

Migration is scoped with you during discovery: which records come across, from which sources, and from what cut-off date. Student, course and faculty data can be imported from spreadsheets. We do not commit to a migration scope before we have seen the source data. The migration checklist helps you prepare.

Both models exist. Institutions can use a hosted service in which each institution's data is kept separate from every other institution's, or a standalone deployment for a single institution. The right model depends on your procurement route and your data policy, and is agreed in the proposal.

Yes. The hosted applications are built to serve multiple institutions, each with its own configuration, users and data.

Payment gateways, biometric attendance devices, email, SMS and WhatsApp messaging, and single sign-on are covered in the integration directory, which states for each whether it is built in, configured per institution, or assessed per project. Integration with another institutional system is assessed case by case.

Training is organised by department around the modules that department will use, as part of implementation. The scope and format are agreed in your proposal.

Existing customers can use the support page, write to support@assoftwaregroup.com, or call +91 70427 31360 on weekdays between 10:00 and 18:00 IST. Support terms for your institution are those in your agreement.

We reply to arrange a time, and ask which offices and workflows matter most so the demonstration covers those. You do not need to prepare anything. If you have used the requirements builder, you can attach its summary to the request.

It depends on the number of students or participants, the modules you take and the deployment model. Tell us those three and we will give you a figure.

Access is controlled by role, and in the student information system by page as well, with two-factor authentication available. What our own staff can access, and when, is governed by your agreement. See security and data handling.