EDMISS https://edmiss.com/ Student Management System Mon, 21 Sep 2026 01:49:28 +0000 en-US hourly 1 https://wordpress.org/?v=7.1.3 Introducing Our Zapier Integration: Connect with 9,000+ Apps and AI Tools https://edmiss.com/features/introducing-our-zapier-integration-connect-with-9000-apps-and-ai-tools/ Mon, 21 Sep 2026 01:39:13 +0000 https://edmiss.com/?p=984 EDMISS brings admissions, marketing, academics, finance, student accommodation and services, compliance, Study Tours, reporting and much more together in one comprehensive platform, supported by powerful built-in capabilities, automations and integrations. And now, we’re expanding what’s possible with our new Zapier integration. Every institution works differently. With Zapier, you can connect EDMISS to more than 9,000 applications […]

The post Introducing Our Zapier Integration: Connect with 9,000+ Apps and AI Tools appeared first on EDMISS.

]]>

EDMISS brings admissions, marketing, academics, finance, student accommodation and services, compliance, Study Tours, reporting and much more together in one comprehensive platform, supported by powerful built-in capabilities, automations and integrations.

And now, we’re expanding what’s possible with our new Zapier integration.

Every institution works differently. With Zapier, you can connect EDMISS to more than 9,000 applications and AI tools, create custom integrations and build workflows around your institution’s unique processes, without writing code for many everyday automations.

Go beyond predefined workflows. Connect the tools you choose, build automations that span multiple systems and put AI to work wherever it adds value.

More flexibility doesn’t mean less control. With granular permissions and Field Access Levels let you control exactly what information each integration can access, helping you protect sensitive student data without limiting what you can automate.

One comprehensive platform. Thousands of connections. More possibilities.

⚡ What is Zapier?

Zapier is one of the world’s leading automation platforms. It connects more than 9,000 applications, from the specialist tools your teams rely on to the enterprise platforms used across your organisation.

Its workflows, called Zaps, connect applications so actions can happen automatically between them. Every Zap starts with a simple idea:

When this happens → automatically do that

But a Zap does not need to stop after one action. It can include multiple steps across different systems, with conditions that decide whether a workflow continues or which path it follows.

For example, a new Student in EDMISS can trigger an approved workflow, check whether specific conditions are met, take different actions based on the result, then continue to the next step. Or a completed process outside EDMISS can create a Student, Offer or Agent automatically.

You choose what starts the workflow, what happens next, which conditions apply and which tools are involved. Zapier moves it forward.

🚀 Imagine what you could connect.

Your website. Your marketing platforms. Specialist services. Enterprise applications. AI tools.

Keep the enquiry and application forms already working on your website, then automate what happens next. A submission can create a Student record and, for an application, a complete Offer in EDMISS, coordinate actions across your chosen platforms and introduce AI where it adds real value.

Keep your systems in sync. When a Student or Agent is created in EDMISS, Zapier can automatically add them to your enterprise CRM, email marketing platform or other approved system. And the workflow can work in reverse, creating a Student or Agent record in EDMISS when the relevant activity starts in an approved external platform.

Automation can also simplify data intake. When a spreadsheet containing student details is uploaded to SharePoint or Dropbox, Zapier can create the Student records in EDMISS automatically. When a new Student is created, it can trigger the next step, such as provisioning their email address.

These are only a few examples. With more than 9,000 applications to connect, you can build workflows that go far beyond predefined integrations and automations.

And it gets even more powerful: your customisations come with you.

The custom fields you create in EDMISS are automatically available in Zapier. That means you can build integrations and automations around the information, workflows and processes that make your institution unique.

Your workflows. Your applications. Your rules.

⚙ Automation on your institution's terms

Every institution has its own processes, services and priorities. You may have an internal system, a group-wide platform, a specialist partner workflow or a digital experience designed for a particular market.

Zapier gives your team flexibility to connect these processes to EDMISS in the ways that make sense for your institution. Many workflows can be built through a visual, no-code interface, helping good automation ideas move faster without becoming a development project first.

Start with a straightforward trigger and action, or build a more advanced workflow with multiple steps, filters, conditions and different paths. This means a workflow can respond to the information it receives, rather than treating every scenario in exactly the same way.

To get you started, our initial Zapier integration includes the following Triggers and Actions:

Triggers
  • Student Created
  • Offer Created
  • Agent Created
  • Agent Employee
Actions
  • Create Students
  • Create Offers
  • Upload Documents
  • Create Agents
  • Create Agent Employees
  • Create Notes
  • and more…

These are building blocks for workflows designed around your needs. A new Agent could trigger an approved partner process. A form submission could create a Student with an Offer. The right workflow is the one that fits how your institution operates.

Student Created → check conditions → follow the right path → complete multiple next steps

✨ Bring AI into the workflow

With Zapier, you can also incorporate AI directly into your workflows, connecting EDMISS with AI tools to summarise information, generate content, analyse data and automate more complex processes.
And you don’t need to build your own AI integration. Zapier provides built-in AI capabilities that you can add as steps in your workflows.

Student Created → approved information sent to an AI step → summarise or classify → continue the workflow

Depending on the tools and processes your institution chooses, AI may help to:

  • Summarise information for staff review
  • Classify or categorise data
  • Extract key details
  • Prepare information for the next step in a process
  • Support more advanced multi-step workflows

This creates room to explore AI use cases while keeping them grounded in the real processes your team manages every day.

🔗 Deep integrations where connectivity matters. Flexibility where it counts.

Zapier adds a new option to our integration strategy. We will continue investing in deep, purpose-built integrations where systems need to work closely together and tight connectivity delivers the best experience.

Zapier complements those integrations with flexible, no-code automation for the systems, services and workflows that are specific to your institution. For advanced requirements and fully custom solutions, our API provides the foundation.

  • Purpose-built integrations for deeply connected experiences
  • Zapier for flexible, no-code automation
  • API for advanced and custom integrations

🔐 More automation, with the right controls

Zapier for EDMISS is powered by our API, giving institutions access to the security and access controls available through the API. Dedicated integration access can be created, permissions can be managed and access can be limited to what each workflow needs.

You stay in control of what information is made available to Zapier. That matters as you connect external services and AI-powered workflows. More automation does not mean giving every connected service access to everything.

Automation on your terms also means access on your terms.

🗓Available from September 2026

Zapier for EDMISS will be available from our September 2026 release and is included with Plus subscription plans.

Access will be available by invitation initially. If you are interested in using Zapier for EDMISS, please contact our support team.

A new level of Integrations and automation

Zapier lets you create your own automations, connect institution-specific systems, bring AI into workflows and move faster without code for many workflows.

And this is only the beginning. We will continue expanding Zapier triggers and actions as institutions find new ways to automate.

The post Introducing Our Zapier Integration: Connect with 9,000+ Apps and AI Tools appeared first on EDMISS.

]]> Introducing Field Access Levels: Greater Control Over Your API Data https://edmiss.com/features/introducing-field-access-levels-greater-control-over-your-api-data/ https://edmiss.com/features/introducing-field-access-levels-greater-control-over-your-api-data/#comments Fri, 04 Sep 2026 04:55:02 +0000 https://edmiss.com/?p=972 We’re introducing Field Access Levels for our API, giving institutions a new level of control over how personal and sensitive information is accessed through the API. As integrations become more powerful and AI agents begin to interact directly with institutional data, controlling access is no longer just about deciding which records an application can see. […]

The post Introducing Field Access Levels: Greater Control Over Your API Data appeared first on EDMISS.

]]>

We’re introducing Field Access Levels for our API, giving institutions a new level of control over how personal and sensitive information is accessed through the API.

As integrations become more powerful and AI agents begin to interact directly with institutional data, controlling access is no longer just about deciding which records an application can see. It is also about controlling which information within those records it can access.

Field Access Levels make that possible.

Each field can now be classified as Standard, Personal or Restricted, adding extra permission controls around personal and sensitive information while still allowing integrations, automations and AI-powered solutions to access the data they need.

🔐 Go Beyond Resource-Level Permissions​

API permissions already control which resources an application can access. Field Access Levels introduce another layer of control within those resources.

For example, an integration may have permission to access student records without automatically receiving access to every field stored against a student.

Fields can be assigned one of three Access Levels:

Standard
General information available when the application has permission to access the relevant API resource.

Personal
Personal information that requires an additional API permission before it can be accessed.

Restricted
Sensitive information that requires an additional API permission before it can be accessed.

For example, student information could be classified as:

  • Standard: Student Name
  • Personal: Student Email Address
  • Restricted: Student Passport Details

 
This gives institutions more granular control over the information exposed through the API.

🔍 Control What Integrations and AI Agents Can See

This becomes particularly important as APIs power more than traditional system-to-system integrations.

Consider an AI agent or reporting integration designed to analyse Offers across your institution.
To perform that task, it may only need access to basic information about the offers and students. It may not need access to the student’s personal contact details or sensitive information such as passport details.

With Field Access Levels, you can establish those boundaries.

An application can access the student resource and its Standard fields, while Personal and Restricted fields remain protected unless the integration user has specifically been granted the additional permissions required to access them.

The same controls apply whether the API is being used by an AI agent, an automation, an internal application or an integration with another system.

🛡 Protect the Data That Matters to Your Institution

Every institution manages different information, so these controls are not limited to the fields provided by default.

Field Access Levels can also be assigned to custom fields.

If your institution creates a custom field containing personal or sensitive information, you can assign the appropriate Access Level and require additional API permissions before an integration can access it.

This means the same access controls can protect both system fields and information specific to your organisation.

🏷 Default Access Levels

We have assigned default Access Levels to Student fields based on the type of information they contain. For example, contact details are classified as Personal, while passport and medical information is classified as Restricted.

These classifications are not fixed. You can review and change the Access Level assigned to both system and custom fields to suit your organisation’s data access requirements.

Field Access Levels are also not limited to the Student object. You can classify fields across other supported objects where you want additional control over the information available through the API.

🔑 New Permissions for Personal and Restricted Data

Two additional permissions are now available for API Roles:

  • View personal data: Allows the integration user to access fields classified as Personal.
  • View restricted data: Allows the integration user to access fields classified as Personal and Restricted.

These permissions are separate from the permissions that provide access to API resources.

This means an integration user may have permission to access Students, for example, but will only receive Standard fields unless it has also been granted permission to access Personal or Restricted data.

🔒 Existing Integrations Remain Protected by Default

To protect personal and sensitive information, we have not automatically assigned either of the new permissions to existing integration users.

This means existing integrations using the API v2 will not receive data from fields classified as Personal or Restricted unless the appropriate new permissions are explicitly granted or the access levels for those fields is set as Standard.

This approach ensures that introducing Field Access Levels does not automatically expand an existing integration’s access to protected information.

However, it also means you should review your existing integrations to determine whether they rely on any fields that are now classified as Personal or Restricted.

⚠ Action Required: Review Your API Access

We recommend reviewing your field classifications and existing integrations using the API v2 to make sure they have the appropriate level of access.

  1. Review your Student and Student Contacts fields
    Check which fields are currently classified as Personal or Restricted and confirm that their Access Levels are appropriate for your organisation.
    You can easily review these from the Object Fields list using the Access Level column. From the same grid, you can also update the Access Level for an individual field or multiple fields at once.

  2. Review what your integrations need
    Determine whether any of your existing integrations need access to fields classified as Personal or Restricted.

  3. Update API Role permissions where required
    If an integration legitimately requires this information, add the appropriate View personal data and/or View restricted data permission to its API Role.


If an integration does not require Personal or Restricted information, no additional permissions need to be granted.

This gives you the opportunity to make a deliberate decision about which integrations can access personal and sensitive data rather than providing that access by default.

⚡ More Powerful Integrations. More Control Over Your Data.

API v2 was built to support a new generation of integrations, automation and AI-powered solutions.

As those possibilities grow, so does the importance of controlling exactly what information each system can access.

Field Access Levels provide another important layer of security and governance within API v2, helping institutions take advantage of connected systems and AI-powered solutions while maintaining greater control over personal and sensitive data.

Connect more. Automate more. Stay in control of your data.

The post Introducing Field Access Levels: Greater Control Over Your API Data appeared first on EDMISS.

]]> https://edmiss.com/features/introducing-field-access-levels-greater-control-over-your-api-data/feed/ 1 EDMISS API Version 2: Built for Humans. Ready for AI. https://edmiss.com/features/edmiss-api-version-2-built-for-humans-ready-for-ai/ Tue, 21 Jul 2026 02:25:49 +0000 https://edmiss.com/?p=855 We’re excited to announce the release of EDMISS API Version 2, a major milestone in the evolution of the EDMISS Next Generation Platform. Built from the ground up, API Version 2 has been designed for a world where systems need to connect faster, workflows need to automate more intelligently, and AI applications need secure, structured, […]

The post EDMISS API Version 2: Built for Humans. Ready for AI. appeared first on EDMISS.

]]>

We’re excited to announce the release of EDMISS API Version 2, a major milestone in the evolution of the EDMISS Next Generation Platform.

Built from the ground up, API Version 2 has been designed for a world where systems need to connect faster, workflows need to automate more intelligently, and AI applications need secure, structured, and reliable access to business data.

Whether you’re building integrations, automating business processes, or developing or using AI solutions, API Version 2 provides the foundation to make it happen.

💡 A New Foundation for Connected Systems ​

API Version 2 is more than a technical upgrade. It is a core platform capability designed to help institutions, partners, and technology teams build smarter connections with EDMISS.

Whether you’re integrating with finance systems, CRM platforms, document management systems, custom applications, or AI-powered assistants, the new API provides a secure and flexible foundation for automation and seamless data exchange.

This is just the beginning. API Version 2 establishes the foundation for future integrations, expanded automation capabilities, and a growing ecosystem of connected solutions around EDMISS.

🛡 Security and Governance Designed for Integration ​

API Version 2 introduces new authentication and governance capabilities that give organisations greater control over how integrations access EDMISS.

The new API introduces dedicated integration users, allowing organisations to separate system access from standard staff access. Each integration user has its own roles and permissions, making it easy to grant only the access required for each integration.

Every API request is performed on behalf of a specific integration user, creating a clear audit trail. Organisations can easily identify whether a change was made by a staff member, a third-party application, a vendor integration, or an AI solution, improving accountability and governance.

Authentication is managed through access tokens issued specifically for dedicated integration users. Each integration, vendor, service, or AI solution can have its own token, allowing access to be managed independently. Administrators can revoke individual tokens at any time without affecting other integrations, providing precise control over API access.

API Version 2 also introduces tenant-level rate limits across both short and long time windows. Daily request monitoring provides visibility into API usage, helping organisations understand adoption, monitor activity, and manage integrations with confidence.

🪄Powerful New API Capabilities​

API Version 2 introduces a range of new endpoints and capabilities designed to make integrations simpler, more flexible, and AI-ready. This is just the beginning, and we will continue to expand the API with new capabilities and endpoints over time.

Current highlights include:

  • Document upload endpoints to automate document collection and storage.
  • Customisable search endpoints that support API-driven reporting and data retrieval by allowing you to:
    • Select only the fields you need, reducing payload size and improving performance.
    • Apply custom filters to retrieve precisely the data required.
  • Custom field support across the API, including filtering and sorting in search endpoints, enabling integrations to work seamlessly with your organisation’s configured data.
  • Utility endpoints that expose the available fields for each object, including their name, description, and data type, making integrations easier to build and maintain.
  • Picklist endpoints that return valid values for supported fields, allowing applications and AI solutions to validate and process data more reliably.
  • Default product values when creating offers. Products can automatically use their configured default pricing and duration, while still allowing integrations to override these values when required.

📋 Interactive API Documentation

API Version 2 includes comprehensive, interactive documentation designed to help developers get up and running quickly.

Developers can explore endpoints, review request parameters, inspect sample requests and responses, understand response structures, and test API calls directly from the browser without needing a separate API client.

For teams using their own development tools, the documentation can also be exported as an OpenAPI specification and imported into popular platforms such as Postman, Insomnia, Swagger, and other OpenAPI-compatible tools. This helps developers and integration partners accelerate development, validate requests, and start building with confidence.

🤖 Ready for AI

One of the most exciting aspects of API Version 2 is how well it supports the next generation of AI-powered applications and autonomous agents.

AI solutions require APIs that are secure, well documented, predictable, discoverable, and capable of describing their own data structures. API Version 2 has been designed with these requirements in mind.

With metadata endpoints, picklist values, custom search capabilities, support for custom fields, meaningful validation errors, dedicated integration users, revocable access tokens, and API usage monitoring, the platform provides the context, security, and governance that both AI solutions and integration teams need to operate safely and effectively.

🔍 API Version 1 Compatibility

We know many customers and partners rely on API Version 1 for their existing integrations. That’s why API Version 1 will continue to be supported, allowing current integrations to keep running without interruption.

As we move forward, our development efforts will focus on expanding API Version 2 by bringing across existing capabilities and introducing new features designed for modern integrations, automation, and AI-powered solutions.

Customers can use API Version 1 and API Version 2 side by side, making it easy to adopt the new API at their own pace. Each API version has its own usage limits, so organisations should plan their integrations accordingly.

✨ What Comes Next

API Version 2 marks the beginning of a new chapter for integrations, automation, and AI across the EDMISS platform.

Over the coming releases, we will continue expanding the API with new endpoints, additional workflows, and enhanced capabilities that help organisations connect EDMISS with the systems, services, and AI solutions they rely on.

Customer feedback will play an important role in shaping what comes next. Whether you’re looking to automate a specific process, integrate with a third-party platform, or enable new AI-powered experiences, we’d love to hear about your requirements and help prioritise the capabilities that will deliver the greatest value.

As more organisations begin building with API Version 2, we’ll also be sharing practical use cases, implementation examples, and ideas to demonstrate what’s possible and inspire new ways to automate and extend EDMISS.

API Version 2 is currently available on an invitation basis. If you’d like to explore how it can support your organisation, we’d be happy to discuss your integration requirements and enable access.

FAQs

Not yet. API Version 1 will continue to be supported for existing integrations. 

Yes. Our development efforts are focused on expanding API Version 2, so we recommend using Version 2 for new integrations wherever possible. 

No. Existing integrations can continue using API Version 1. You can adopt API Version 2 whenever you’re ready and migrate at your own pace.

Yes. Both versions can be used simultaneously. This allows existing integrations to continue on Version 1 while new integrations are developed using Version 2. 

Each API version has its own usage limits. Organisations should consider these limits when designing integrations and automation workflows. 

No. If you already have access to API Version 1, you can also use API Version 2 at no additional cost.

Yes. API Version 2 has been designed with AI in mind, providing secure access, comprehensive documentation, metadata endpoints, and other capabilities that make it easier to build AI-powered applications and autonomous agents.

All use of the API, including AI-powered solutions, must comply with the EDMISS Customer Terms of Service.

For more information about API Version 2, including how to access the technical API Reference, visit our Support Centre: https://support.equatorit.com/nextgen/published/edmiss/equator-api-v2

API Version 2 is being rolled out gradually to customers. If you would like early access or have an integration project you are planning, please contact our Support team. We’ll be happy to discuss your requirements and help you get started.

The post EDMISS API Version 2: Built for Humans. Ready for AI. appeared first on EDMISS.

]]> Introducing the EDMISS + Flywire Integration: Smarter Student Payments Made Simple https://edmiss.com/features/introducing-the-edmiss-flywire-integration/ Wed, 24 Sep 2025 02:25:03 +0000 https://edmiss.com/?p=818 Student payments should be simple and secure. That’s why we’ve partnered with Flywire, a global leader in education payments. Together, we’re making it easier than ever for institutions to receive, process, and reconcile both international and domestic payments, while giving students and families a smoother, more transparent experience. Powered by Flywire’s global payment network and […]

The post Introducing the EDMISS + Flywire Integration: Smarter Student Payments Made Simple appeared first on EDMISS.

]]>

Student payments should be simple and secure. That’s why we’ve partnered with Flywire, a global leader in education payments.

Together, we’re making it easier than ever for institutions to receive, process, and reconcile both international and domestic payments, while giving students and families a smoother, more transparent experience.

Powered by Flywire’s global payment network and 24/7 multilingual support, this integration streamlines the entire payment journey from start to finish

💡 Why This Matters

Schools face real challenges when handling payments:

  • Unidentified transactions that cause manual reconciliation headaches
  • Short balances or overpayments due to unexpected fees or errors
  • Fraud risks when bank details are publicly displayed
  • Students frustrated by hidden costs, unclear instructions, or lack of support
  • Delays in receiving funds, especially for international payments

The EDMISS + Flywire integration solves all of this in one seamless solution—helping schools save time, reduce risk, and improve the overall student experience.

✅ Benefits for Your Institution

With the new integration, your school can:

  • Accept payments in 140+ currencies across 240+ countries and territories
  • Offer a best price guarantee on local currency transfers
  • Eliminate short balances and overpayments with pre-filled payment amounts
  • Automatically link payments to the correct student record
  • Capture all required student details to avoid unidentified payments
  • Enhance fraud protection by removing the need to publish bank details

✨A Better Experience for Students & Families

Students will enjoy:

  • Flexible, convenient payment options with no hidden costs
  • Real-time payment tracking via email, SMS, or the Flywire app
  • 24/7 multilingual support (chat, phone, email, and WeChat)
  • Secure transactions in their local currency with upfront pricing
  • Peace of mind knowing their payments are safe and transparent.

How It Works

You can offer payments through Flywire in two ways:

Option 1: School-Initiated Payment Requests
  1. Schools create templates with a Flywire bookmark to request payments against offers, enrolments, and invoices.
  2. When sending emails, SMS, or merged documents from EDMISS, a unique and secure payment link (or QR code) is generated with the amount due.
  3. Students click or scan to make their payment via Flywire’s secure portal.
  4. Payments are automatically recorded in EDMISS for fast reconciliation.

Payments can be requested for students, offers, enrolments and invoices.

Option 2: Student-Initiated Payments
  1. Students log in to their EDMISS portal.
  2. Go to the Invoices page and select invoices to pay.
  3. Choose Flywire as the payment option.
  4. Pay via bank transfer, card, or other local methods—with no hidden fees.
  5. Track payments in real time with instant updates from Flywire.
  6. Payments post automatically in EDMISS for easy reconciliation.

Start simplifying payments with EDMISS + Flywire. Contact us today.

The post Introducing the EDMISS + Flywire Integration: Smarter Student Payments Made Simple appeared first on EDMISS.

]]> Introducing Agent Contracts https://edmiss.com/features/introducing-agent-contracts/ Thu, 28 Aug 2025 23:49:33 +0000 https://edmiss.com/?p=806 We’re excited to introduce Agent Contracts (available from the August 2025 release). This powerful new feature is designed to help colleges better manage and streamline their relationships with agents. 🤝Organise Your Agent Relationships Think of Agent Contracts as your central hub for managing agent agreements. Instead of scattered details, you now have one place to capture […]

The post Introducing Agent Contracts appeared first on EDMISS.

]]>

We’re excited to introduce Agent Contracts (available from the August 2025 release). This powerful new feature is designed to help colleges better manage and streamline their relationships with agents.

(more…)

The post Introducing Agent Contracts appeared first on EDMISS.

]]> Introducing Automated Invoice Reminders https://edmiss.com/features/introducing-automated-invoice-reminders/ Tue, 24 Jun 2025 23:33:02 +0000 https://edmiss.com/?p=738 Let’s face it—chasing overdue invoices is nobody’s idea of a good time. It’s tedious, awkward, and it takes you away from the work that really matters. That’s why we’ve added a new time-saving feature to eBECAS/EDMISS Next Generation: Automated Invoice Reminders. Get Paid Faster—Without Lifting a Finger With Automated Invoice Reminders, EDMISS NextGen can now send email […]

The post Introducing Automated Invoice Reminders appeared first on EDMISS.

]]>

Let’s face it—chasing overdue invoices is nobody’s idea of a good time. It’s tedious, awkward, and it takes you away from the work that really matters. That’s why we’ve added a new time-saving feature to eBECAS/EDMISS Next Generation: Automated Invoice Reminders.

Get Paid Faster—Without Lifting a Finger

With Automated Invoice Reminders, EDMISS NextGen can now send email or SMS nudges to students (or whoever’s footing the bill) before or after the due date—no manual follow-up required. Just set your reminder rules once and let the system handle the rest.

Whether it’s a polite “your invoice is due soon” or a firmer “you’re overdue,” your reminders go out like clockwork every day.

Here’s Why You’ll Love It

🔁 Fully Automated: Daily batch processing means reminders go out while you’re sleeping (or sipping coffee).
📬 Flexible Messaging: Create multiple reminders with different triggers, tones, and timing.
📡 Multi-Channel Delivery: Send reminders via email or SMS, depending on your audience and urgency.
📎 Attach Documents: Include files like invoices directly in the email for added clarity.
🗒 Automatic Diary Entries: All messages sent are logged in the Student Diary for complete visibility.
✉ Custom Sender Options: Choose to send emails from an individual user account or a college-wide address—your choice
📊 Track Everything: Stay on top of your reminders with detailed logs that show the status, when each message was sent, whether it was successful, and why it failed if not.
🔍 Full Visibility: Preview which invoices will get reminders using your regular invoice search filters.

Smart Rules, Smarter Cash Flow

Setting up reminders is easy—and powerful. You can fine-tune who gets what, and when, using flexible filters such as:

  • Number of days before or after the due date — schedule early nudges or overdue prompts with precision
  • Minimum invoice amount — avoid sending reminders for low-value invoices
  • Payer/Student type — target exactly the right group

Combine these filters to match your collections strategy and create as many reminders as your plan allows. The result? More control, less chasing.

Built-In Efficiency, Designed for You

Whether you’re handling tuition fees, enrolment charges, or any other payments, this feature keeps your cash flow moving and your inbox quieter. Best of all? It’s built into NextGen and works straight from your existing workflows.

No awkward follow-ups. No lost invoices. 

The post Introducing Automated Invoice Reminders appeared first on EDMISS.

]]> Introducing Multi-Factor Authentication and Enhanced Password Policies https://edmiss.com/features/introducing-multi-factor-authentication-and-enhanced-password-policies/ Tue, 23 Jul 2024 00:36:03 +0000 https://edmiss.com/?p=656 In today’s digital age, security is more important than ever, especially when it comes to managing your sensitive data. That’s why we’re excited to introduce two powerful new features to EDMISS: Multi-Factor Authentication (MFA) and Enhanced Password Policies.  These additions are designed to provide an extra layer of protection for your system data, ensuring that […]

The post Introducing Multi-Factor Authentication and Enhanced Password Policies appeared first on EDMISS.

]]>

In today’s digital age, security is more important than ever, especially when it comes to managing your sensitive data. That’s why we’re excited to introduce two powerful new features to EDMISS: Multi-Factor Authentication (MFA) and Enhanced Password Policies. 

These additions are designed to provide an extra layer of protection for your system data, ensuring that only authorized users have access.

Multi-Factor Authentication

Multi-Factor Authentication (MFA) is a security mechanism that requires users to provide two or more verification factors when they log in. One factor is something the user knows, such as their username and password. Other factors include something the user has such as an authenticator app on a mobile phone or a security code on their email or phone. 

By adding additional factors to verify the users’ identity, MFA makes it harder for common threats to succeed.

Why is MFA Important?

Passwords alone are no longer enough to protect against the sophisticated cyber threats we face today. MFA significantly reduces the risk of unauthorized access, even if a password is compromised. By requiring a second form of verification, MFA ensures that the access to your data remains secure.

How Does MFA Work in EDMISS?

Implementing MFA in our Student Management System is straightforward and user-friendly.

Here’s how it works:

  1. Login Attempt: When a user logs in, they will enter their username and password as usual.
  2. Verification Prompt: After entering the correct password, the system will prompt the user for a second form of authentication. This could be a code sent to their email or a code from an Authenticator app installed on their mobile phones.
  3. Access Granted: Once the second form of authentication is successfully completed, the user is granted access to the system.
What MFA Methods are Available?

We understand that convenience and accessibility are crucial when implementing new security measures. That’s why we offer two methods for Multi-Factor Authentication (MFA): Email Verification and an Authenticator App:

  • Email Verification (available in EDMISS Classic and Next Generation): After users enter their username and password, they will receive a short-lived code sent to their email address. They must enter this code before it expires to complete the authentication process.

    When this method is enabled, MFA will be enforced for the entire organization (users cannot opt-out individually).

  • Authenticator App (only available in EDMISS Next Generation): With this method, after users successfully enter their username and password, users need to get a code from their authentication app of preference and enter it to complete the authentication process.

    This is an opt-in method that users need to enable and set up individually.
    When enabled, this method takes preference over the email verification method (if enabled).

At this first phase, MFA is not available for the teacher and student portals.

Trusted Devices

To enhance user convenience while maintaining security, when MFA is enabled (email verification) users can mark their devices as “trusted.” This means that once a device is trusted, users can skip the MFA process on that device for a period defined by the system administrator.

Enhanced Password Policies

Alongside Multi-Factor Authentication, we are also introducing enhanced password policies to further safeguard your data. 

These policies include:

  • Minimum Length Requirements: Ensures that all user passwords meet a required length
  • Password Complexity Requirements: Mandates the use of varied character types in user passwords
  • Password Expiration: Enforces regular changes to user passwords after a specified period
 

These policies can now be customized by the system administrator to better align with their organization’s specific needs.

These policies apply to all administrative users and teachers using EDMISS Classic, EDMISS Next Generation and EDMISS Teacher Portal.

Getting Started with MFA and Enhanced Password Policies

Setting up these new security features is easy, follow these links for the details.

If you have started using EDMISS Next Generation (currently in BETA), you can make changes in either system, and they will apply to both.

EDMISS Classic (Desktop version)

 

EDMISS Next Generation (web version)

Preparing your Users for Multi-Factor Authentication

If you are enforcing MFA (email verification), ensure all your users have a valid email address that they can access during their login process. If they do not have a valid email address or cannot access it during the log in process, they will be unable to complete the authentication process.

Please note that these features are available from version 12.1.0.0.

We’ve started rolling out these features and they will be available to all colleges in the next weeks.

The post Introducing Multi-Factor Authentication and Enhanced Password Policies appeared first on EDMISS.

]]>