Centralized
Administration
& Security

Role-based permissions let you control who can view, edit, or export contacts. You can restrict by team/agency, hide sensitive fields, and keep a full audit trail.

Yes. Admins can define global custom fields, dropdowns, and validation rules once and reuse them across forms and modules—keeping data consistent and governance simple.

Absolutely. Every critical change is logged (who, what, when, where) with exportable audit trails to support compliance, investigations, and internal reviews.

Yes. HEM-SP includes a built-in CRM and also integrates with external CRMs such as Mautic, Salesforce, and HubSpot, as well as major LMS and campus systems via APIs and webhooks. This allows you to sync contacts, applications, enrollments, and grades between systems, reducing duplicate data entry and keeping every team aligned.

Student data is encrypted at rest (database and file storage) and in transit (TLS/HTTPS), protected by AWS security groups, web application firewalls, and regional data residency (Canada and EU). The platform is designed to support GDPR and FERPA compliance with role‑based access control, audit logging, and strong authentication, and payment flows are PCI DSS SAQ‑A compliant with card data handled entirely by certified gateways such as Stripe, PayPal, Helcim, Flywire, and Moneris.

Yes. You can configure multiple campuses, programs, and courses—and associate students and cohorts with one or more campuses as needed. The platform supports multiple branded portals and subdomains, and application forms and content can be localized so you can serve different regions, brands, or languages from one underlying system.

Log in as an administrator and open the Settings or Administration area from the left‑hand navigation. From there you can manage global school settings such as campuses, programs, branding, integrations, and communication defaults.

Yes. The portal supports school‑branded applicant portals, application forms, and subdomains, so you can configure logos, colours, and basic styling to align closely with your institution’s brand.

Yes. Authorized staff can impersonate users to see the portal exactly as a student (or agent) sees it, which is helpful for support and training. Impersonation is permission‑controlled and audited so you maintain full transparency over who accessed which account and when.

The Settings and User Permissions module lets you create roles (e.g., Admissions, Finance, Marketing, Leadership) and assign granular permissions per module such as Applicants, SIS, Finances, Reports, and Settings. For external partners, agent permissions (Regular Agent, Agency Admin, Super Admin) control what each user can see and edit.