LearnNeat

Different user types have different default login credentials in the system:

🎓 For Students:

Username: GR Number (General Register Number)
Password: Date of Birth in DDMMYYYY format
Example:
Username: 2025000001
Password: 01012010 (for DOB: 1st Jan 2010)
School Code : SCH20251

👥 For Parents, Teachers, and Staff:

Username: Email Address
Password: Mobile Number
Example:
Username: teacher@school.com
Password: 9876543210
School Code : SCH20251

Note: For security reasons, it's recommended to change these default passwords after first login.

🔄 Admin Panel Update
Step-by-Step Guide:

Login as Super Admin

Use your Super Admin credentials to log in to the system.
Go to System Update

In the left-side menu, scroll to the bottom and click on the "System Update" option.
Enter Purchase Code and Upload File

In the "Purchase Code" field, enter your valid purchase code.
In the "Files" section, click on "Choose File" and upload the nearest version update file.
Important Note About Versioning

You must update the system step-by-step.
For example, if your current Admin Panel version is v1.5.5, then you should upload the v1.5.6 update file.
Do not directly upload a higher version like v1.7.0, or the update may fail.
Submit and Wait

Click the "Submit" button and wait for a few moments.
The system will process the update, and your Admin Panel will be upgraded.
📹 Video Tutorial Available: A detailed video tutorial is available below the update section to guide you visually through the process.

📱 App Code Update
There are two methods available for updating your App Code:

Option 1: Manual Update (Recommended for Non-Technical Users)
When an update is released, you will receive the updated app source code via email.
Inside the update package, you will find a file called change_log.txt or similar.
This file contains:
A list of files that were modified.
A list of new files that were added.
Open the latest version code and manually copy the updated and new files into your existing project as per the change log.
After copying and replacing the required files, your app will be successfully updated.
Option 2: Full Reskin Method (Recommended for Developers / Technical Persons)
This method is faster and preferred by technical users who are familiar with Flutter and Firebase.

Steps:

Download the Latest Full App Code (from the update mail or portal).
Perform the following changes in the new code:
Change the App Name (for both Android and iOS).
Change the Package Name (bundle identifier).
Replace the Firebase configuration using firebase_cli or manually add the updated Firebase project.
In the constants.dart file, update the Base URL to match your backend server.
Replace the App Icon and other branding assets you used in the previous version.
After completing these steps, build and run the new app code. It will function the same as your previous version but with the latest updates applied.

Setting up a wildcard domain involves creating a DNS record and configuring it properly in your hosting panel.

Note: Since the steps can vary depending on the hosting provider or control panel (e.g., cPanel, Plesk), we recommend contacting your hosting support team for detailed guidance on setting up wildcard DNS records.

Common Steps:

Access your domain's DNS management panel
Create a new DNS record with type A or CNAME
Set the hostname to * (wildcard)
Point it to your server's IP address or domain

Wildcard SSL setup depends on your hosting provider and the type of SSL certificate you need.

Recommended Action: Please reach out to your control panel or hosting support to request and install a wildcard SSL certificate for your domain (e.g., *.yourdomain.com).

Common Options:

Let's Encrypt (free, with limitations)
Commercial SSL providers (paid, more features)
Hosting provider's SSL services

The behavior depends on the "Instant Effect" setting when updating the package:

✅ Instant Effect Enabled:

Only the features are updated immediately
Existing subscribers get the new features right away
❌ Instant Effect Disabled:

The updates won't apply immediately
The school will continue with the existing features until the current plan expires
New features will be available upon plan renewal
Best Practice: Always review the "Instant Effect" setting before updating packages to avoid unexpected changes for active subscribers.

Addon validity is always tied to the school's current subscription plan expiry date.

Key Points:

The addon will expire along with the school's main package
This applies regardless of when the addon was activated
Addons cannot extend beyond the main subscription period
Example:

Main subscription expires: December 31, 2024
Addon activated: November 1, 2024
Addon expires: December 31, 2024 (same as main subscription)
Recommendation: Plan your addon purchases to align with your main subscription renewal cycle.

The School Code is a unique identifier assigned to each school. You can find it from both the Super Admin Panel and the School Admin Panel:

🔹 From the Super Admin Panel:

Navigate to: Schools → Manage Schools
Click the column selector icon (top-right of the table)
Enable the "Code" column by checking it
You'll now see the School Code in the table listing
e-School SaaS

🔹 From the School Admin Panel:

Go to: System Settings → General Settings
Look for the School Code field on the right side of the form
e-School SaaS

In our system, "Classes" (also known as "Grades" in some countries) represent the academic levels students are enrolled in — for example, Grade 1 through Grade 12.

Each Class can have multiple Sections. A Section is essentially a sub-division of a class, created to manage students efficiently when the number of enrolled students exceeds the capacity of a single classroom.

Why Sections Are Needed:

Let's take an example:

Suppose your classroom capacity is 30 students.
For Grade 1, if 90 students apply for admission, it's not feasible to place them all in one classroom.
In such a case, the system allows you to create multiple Sections under the same Class — such as Grade 1 - A, Grade 1 - B, and Grade 1 - C.
Each section can then accommodate up to 30 students, depending on classroom size or academic management preferences.
How It Works in the System:

Create a Class (e.g., Grade 1)
Create Sections (e.g., A, B, C)
Assign Students to Sections — This can be done manually or based on performance, alphabetical order, or admission order.
The system ensures students are evenly distributed according to section capacity, and each section can be managed individually.
Benefits:

Better classroom and resource management
Improved teacher-to-student ratio
Easier tracking of student progress within smaller groups

e-School SaaS
This issue usually occurs when the API headers are not correctly formatted, specifically the school-code field.

In the api.dart file inside the headers() method, make sure the key is written as:

"school-code": schoolCode ✅ Correct

e-School SaaS

⚠️ Do not use an underscore (_) like this:

"school_code": schoolCode ❌ Incorrect

Using school_code with an underscore causes the backend to reject the request due to a mismatch in expected header keys, leading to the "Something went wrong" error on the app screen.

To set up Firebase using the Firebase CLI for eSchool SaaS:

Prerequisites:

Make sure you have Node.js installed on your system
Install Firebase CLI:

npm install -g firebase-tools

Log in to Firebase:

firebase login

This will open a browser window where you can authenticate with your Google account.

Video Guide: Watch this quick video guide for a visual walkthrough.

📹 Watch Video Tutorial

Click the link above to watch the Firebase CLI setup tutorial video.

The eSchool SaaS mobile applications provide a convenient feature that allows you to control the visibility of default login credentials on the login screens. This can be helpful for demonstration purposes or to guide users during initial login, but you may want to hide them in production for security reasons.

Location of Configuration:

The configuration is located in the constants.dart file of your Flutter application code.

Available Configuration Variables:

There are two separate boolean variables that control default credential visibility for each app:

📱 For Student App:
showDefaultCredentialInStudentApp = true; // Shows default credentials
showDefaultCredentialInStudentApp = false; // Hides default credentials

When set to true:

The Student App login screen will display example/default credentials including:
GR Number (General Register Number) example
Password (Date of Birth format) example
School Code example
This helps students understand what information they need to enter
When set to false:

The default credentials will not be shown on the login screen
Users will see empty input fields without any placeholder examples
Student App Default Credentials Configuration

👥 For Staff/Teacher App:
showDefaultCredentialInTeacherApp = true; // Shows default credentials
showDefaultCredentialInTeacherApp = false; // Hides default credentials

When set to true:

The Teacher/Staff App login screen will display example/default credentials including:
Email address example
Password (Mobile number) example
School Code example
This helps staff members understand the login format
When set to false:

The default credentials will not be shown on the login screen
Users will see empty input fields without any placeholder examples
Staff App Default Credentials Configuration

🔧 How to Configure:
Open the Flutter Project:

Navigate to your Student App or Staff App source code
Locate the constants.dart file:

The file is typically located in the lib/utils/ or lib/constants/ directory
Find the Configuration Variables:

For Student App: Look for showDefaultCredentialInStudentApp
For Staff App: Look for showDefaultCredentialInTeacherApp
Set the Value:

Set to true if you want to display default credentials
Set to false if you want to hide them
Rebuild the Application:

After making changes, rebuild and deploy your application
The changes will take effect in the new build
⚙️ Best Practices:
✅ When to Show Default Credentials (true):

During testing and development phase
For demo or presentation purposes
When onboarding new users who need guidance
In training or educational environments
❌ When to Hide Default Credentials (false):

In production environments (recommended for security)
When users are familiar with the login process
To maintain a professional appearance
To prevent confusion about actual credentials
📝 Important Notes:
These settings are independent for each app (Student and Staff)
The default credentials shown are examples only and do not provide actual access
Users must still enter their valid credentials to log in
This feature only controls the visibility of example text on the login screen
Changes require rebuilding the application to take effect
🔒 Security Recommendation:
For production environments, it is strongly recommended to set both variables to false to maintain a clean and professional login interface without displaying any example credentials.

What are the default login credentials for different Users?

How to Update the System (Admin Panel and App Code)?

How do I set up a wildcard domain (e.g., *.yourdomain.com)?

How do I create a wildcard SSL certificate?

What happens if the Super Admin updates an existing subscription package?

How is the addon validity calculated?

Where can I find the School Code?

How do Classes and Sections work in the system?

Why does the app show "Something went wrong. Please try again later" after login?

How do I set up Firebase using the Firebase CLI for eSchool SaaS?

How can I control whether default login credentials are displayed on the Student App and Staff App login screens?