Clear answers about PACE IMS.

Only Gmail accounts authorised by the PACE administrator can access the internal dashboard.

No. Access can be restricted by role, module and branch. Director-level users may be permitted to view consolidated records.

No. Public information pages are separate from the protected dashboard and do not provide database access.

PACE IMS uses Google sign-in and does not store a separate PACE password. Recover the Google account or contact the PACE administrator.

Yes. The admission workflow captures candidate, parent, education, address, fee, photo, document and declaration details.

Yes. A successful admission creates the connected student record and PACE identifiers.

Yes. The current Click-to-Chat action prepares an admission welcome message and logs the action as OPENED, not SENT.

The CRM foundation supports branch ownership, course interest, stage, priority and follow-up tracking.

Yes. Staff can manage fee instalments, receipts, outstanding balances, manual attendance and imported device-punch records. PDF receipt generation and online payments remain in rollout.

The punch register is active, but automatic device synchronisation is not connected. It will be released only after privacy, offline-sync and six-branch testing are complete.

Staff can manage the student and guardian access registry. Public family sign-in remains disabled until PACE approves the account policy and notification channel.

Yes. Staff can publish assignments, register submissions, record scores and add feedback. Direct student self-upload will activate with the public portal.

Not yet. PACE IMS is being proven inside PACE first. Other institutions may register interest for the future edition.

No public subscription price has been set because the external edition and support scope are still being defined.

No. A commercial edition would require isolated institution data, independent onboarding and separate access controls.