Edsby

No data left to chance

Info in Edsby is determined by customer systems of record.

Consistent, effortless dataflow

Advanced two-way sync with existing systems of record drives everything Edsby does. It’s how classes are set up. It’s how timetables and schedules are populated. It’s how attendance and achievement data get saved back. Edsby can’t even work standalone. It HAS to be driven by official systems.

No user account loopholes

Edsby accounts are only created by sync with student information/management, single sign-on and/or other systems. As user accounts come and go, changes reflect in Edsby. Eliminates privacy risk of someone adding users, forgetting to remove them, etc.

No data left to chance

Only the right people get access

There's no separate permissions system to manage in Edsby.

Edsby security best practices

Customer determines access

At initial integration, customers determine which roles in their existing systems get to do what in Edsby. Roles are programmatically mapped to specific permissions in Edsby.

Bad actors kept out

Local or regional multi-factor authentication (MFA) is supported via single sign-on with Google or M365. Ensures only valid, current users can ever log in.

Parent access to records

Parents' electronic access to their children's student data is securely controlled.

Parent access managed

Parents might or might not be recorded in the official SIS/SMS. They might not even be managed in a database at all. Edsby can work in any scenario and yet provide secure parent access to their children’s info. And as parent/child relationships change due to custody or other factors, those changes can reflect in Edsby.

Parents get the right access

Parents can’t access information they shouldn’t in Edsby. They only see what teachers have specifically shared in their children’s current classes, and only see information on their child. They cannot view posts or even profile photos of anyone other than their child.

Edsby parent engagement

Best practice cybersecurity & system protection

As the national K-12 data framework for several countries and states/provinces, Edsby is subject to higher levels of security and privacy scrutiny

Edsby and the right people access

Data sovereignty

All data and backups reside in a customer’s selected geographic region.

ISO 27001

Edsby and its data practices are certified every year to ISO 27001 standards.

Penetration tests

As part of certification requirements and ongoing requalification by national customers, Edsby is regularly subjected to third party security assessments.

End-to-end encryption

All Edsby data is encrypted in transit and at rest. Passwords are never transmitted in clear text.

All admin tools firewalled

All administrative tools are protected with multi-factor authentication to ensure only active, trusted users can access them.

Data deletion

Data is retained in Edsby only as long as required by customers’ own policies.

Activity monitoring & logging

All activities in Edsby are logged for compliance, governance and law enforcement.

Compliance with regs

Edsby adheres to requirements of FERPA, COPPA, PIPEDA, GPDR and other student data regulations worldwide.

Contact Edsby

How can we help you?

Contact Sales