Hyland OnBase is an enterprise content and process-management platform that captures, governs, and delivers documents and data connected to operational work. Districts can use it for student and employee records, finance, contracts, facilities, case files, and other processes that require secure content, structured workflows, and an audit history.

A document repository can span many departments with different record owners and access needs. Student, personnel, and finance identifiers provide context for the supporting content used in operational decisions. A document’s identifier, approved version, and relationship to a person or transaction supply its administrative meaning. Full-text search alone cannot establish which version supports a particular action.

Changes to indexing, retention rules, or approval flows can affect several departments and connected processes. Teams coordinate authorized versions and the relationship between supporting documents and operational transactions. Understanding the environment includes how completed actions are recorded, how access changes, and which repository holds the authoritative evidence for a decision.

iboss is a cloud-delivered security service edge and web-security platform that applies internet access, threat protection, and data controls to users and devices on or off the district network. Its K–12 offering combines CIPA-oriented filtering with malware defense, SSL inspection, reporting, and student-safety visibility.

User and device context connect internet policy to activity across locations. Network and identity teams coordinate enforcement and investigate how filtering decisions affect access to instructional and business services. Security events need their account, device, and network context. IT staff coordinate policy changes with the services that depend on continued authorized connectivity.

Identity Automation's RapidIdentity is an education-focused identity and access management platform. It uses student, staff, guardian, contractor, and other identity data to automate account creation and removal, deliver role-based single sign-on, apply multi-factor authentication, manage access requests, and distribute class rosters to connected applications.

Enrollment, employment, and role changes become access decisions here. SIS and HR owners supply the underlying facts, while technology staff translate those facts into accounts, groups, and application permissions. An account, an application permission, and a class membership are different relationships. Their source, timing, and approval determine what a person can actually do after signing in.

A transfer, departure, or duplicate identity can affect several applications at once. District teams coordinate matching, authorization, update timing, and exceptions across the deployed connections. Sign-in, account creation, and roster sharing are related processes with different purposes; understanding each boundary helps explain why access may succeed in one service and fail in another.

Infoblox provides DNS, DHCP, and IP address management together with DNS-layer security and network visibility. Districts use it to operate core network addressing services, maintain authoritative records of devices and subnets, detect malicious or anomalous DNS activity, and block access to known harmful infrastructure.

Device addresses and name resolution underpin access to many district applications. Network staff coordinate authoritative records, security policies, and changes because faults in these services can disrupt otherwise healthy systems. A request may pass through several network services before reaching an application. Location, device, address, and policy context help explain where a failure or access decision occurred.

A change to routing, naming, addressing, or access policy can affect multiple schools and departments. IT teams coordinate approval, testing, maintenance timing, and response to faults with the affected service owners. Its place in the district is foundational: a healthy application can still be unavailable when the network relationship it relies on is incorrect.

Insignia Library System is an integrated library platform for school, public, academic, and special libraries. Its Enterprise configuration supports centralized administration across multiple branches while managing cataloging, circulation, patrons, acquisitions, serials, discovery, inventory, and reporting.

Central administration links branch-level collections and patron activity. Librarians maintain material records while school and technology staff help align borrower identities and access across participating sites. The patron record and the item record have separate maintenance needs. Library, SIS, and technology staff coordinate their relationship through school changes and annual rollover.

Integrify is a low-code workflow and approval platform for replacing email and paper processes with online requests, conditional routing, tasks, notifications, forms, and audit histories. Districts can configure it for purchasing, HR actions, access requests, policy review, facilities approvals, and other administrative processes.

A routed request records who submitted, reviewed, approved, and completed an action. Process owners connect that history with the final update required in finance, HR, facilities, or another operational system. A completed approval and a changed operational record may be separate events. Process owners establish responsibility for that final handoff and the evidence retained.

Jamf Connect is Mac identity and access software that connects local account workflows with a cloud identity provider. Jamf Connect supports authentication and password alignment so organizations can manage access to Macs with their established identity environment. School IT teams can align Mac sign-ins with institutional accounts.

The relationship between a local Mac account and a cloud identity shapes access. Mac and identity administrators coordinate sign-in changes, account recovery, and employee or student transitions.

Jamf Pro is an Apple-focused endpoint management platform for districts with substantial Mac, iPad, iPhone, Apple TV, and other supported Apple deployments. It helps technology teams automate enrollment, configure devices, distribute applications and updates, maintain inventory, enforce security requirements, and provide approved resources to users.

Apple device administration connects enrollment, application distribution, and school-managed identities. Device and identity teams coordinate assignments and settings so configuration follows the intended user or location. Configuration and assignment are related but different records. Device administrators coordinate those sources with identity and inventory owners when school or user circumstances change.

Jamf School is a cloud Apple device-management platform designed specifically for K–12 environments. It helps district and school staff enroll, configure, inventory, update, and secure institutionally owned Mac, iPad, iPhone, and Apple TV devices while organizing administration around schools, classes, teachers, and students.

Class and school membership give Apple device policies their local context. Technology staff coordinate managed identities, application access, and device assignments as learners and equipment move through the school year. Configuration and assignment are related but different records. Device administrators coordinate those sources with identity and inventory owners when school or user circumstances change.

Atlassian Jira is a configurable work-management and issue-tracking platform for projects, service delivery, software development, operations, and structured requests. District teams can use boards, lists, workflows, forms, queues, automation, and reports to track work from intake through completion.

An issue links a request with assigned work, dependencies, and completion evidence. District process owners configure the workflow and decide how its outcome connects with other administrative records.

KACE Service Desk by Quest is a ticket-management system for IT support organizations. It accepts requests through self-service, email, web, or staff channels and provides configurable queues, fields, workflows, knowledge resources, service levels, and reporting.

The ticket provides the link between the reported problem and the people responsible for resolving it. Consistent queues and classifications make service patterns visible beyond individual technicians’ inboxes. Consistent request types, locations, and status definitions help teams interpret workload and service outcomes without losing the detail of individual cases.

Koha is a free and open-source integrated library system for cataloging, circulation, patrons, acquisitions, serials, authorities, reporting, notices, and public discovery. It supports single libraries, multi-branch systems, and consortia through browser-based staff and patron interfaces.

Patron and item identifiers connect borrowing activity across branches. Library and technical staff coordinate imports, local configuration, and hosting responsibilities so catalog and circulation records remain usable. The patron record and the item record have separate maintenance needs. Library, SIS, and technology staff coordinate their relationship through school changes and annual rollover.

Laserfiche is an enterprise document-management and process-automation platform that helps districts capture, organize, search, secure, retain, and act on administrative content. It can support records across human resources, finance, student services, contracts, public records, and other departments that need controlled access and repeatable workflows.

Electronic records and routed forms connect departmental work that crosses several systems. Records managers, business owners, and IT staff coordinate indexing, access, retention schedules, and the completion of approved actions. A document’s identifier, approved version, and relationship to a person or transaction supply its administrative meaning. Full-text search alone cannot establish which version supports a particular action.

Changes to indexing, retention rules, or approval flows can affect several departments and connected processes. Teams coordinate authorized versions and the relationship between supporting documents and operational transactions. Understanding the environment includes how completed actions are recorded, how access changes, and which repository holds the authoritative evidence for a decision.

Level Data Directory Integration Services automate the movement of student and staff identity information from K–12 SIS and HR systems into Microsoft Active Directory, Microsoft Entra ID, and Google Workspace. The service creates and updates accounts, groups, email addresses, organizational placement, and other attributes according to district-defined business rules.

Employment and enrollment facts become directory accounts, groups, and attributes. HR, SIS, and IT teams coordinate source authority and effective dates so changes lead to the intended access outcome. An account, an application permission, and a class membership are different relationships. Their source, timing, and approval determine what a person can actually do after signing in.

A transfer, departure, or duplicate identity can affect several applications at once. District teams coordinate matching, authorization, update timing, and exceptions across the deployed connections. Sign-in, account creation, and roster sharing are related processes with different purposes; understanding each boundary helps explain why access may succeed in one service and fail in another.

Level Data Integration Services is a managed K–12 interoperability offering that automates data movement between a district's SIS or HR system and the operational applications that depend on it. Typical connections provision directory accounts and keep food service, transportation, library, learning, assessment, and other systems synchronized without district staff maintaining separate integration scripts.

One source correction can affect several receiving services. District application owners and technical staff coordinate field meaning, update schedules, and exception handling so synchronization preserves the operational intent of the data. A successful transfer can still carry a mismatched identity or an inappropriate field value. Source ownership and agreed receiving rules give the technical exchange its business meaning.

The work continues after the first successful exchange. A source correction, new school year, vendor update, or failed transfer can change what receiving applications know. Application owners and technical teams coordinate monitoring, exception review, and approved changes so that synchronized data continues to represent the intended students, staff, classes, and services.

Lightspeed Filter is web-content filtering software for school-managed devices. Lightspeed Filter applies district browsing policies, manages access to online content, and provides activity reports for administrators.

Browsing decisions depend on configured policy and the requesting account or device. IT teams maintain that context when resolving access problems and reviewing activity across the school environment. Policy enforcement and student-support decisions have different owners. Browsing data needs appropriate access and context when used beyond troubleshooting or access administration.

Lightspeed Insight is education technology analytics software for understanding digital application use and supporting app governance. Lightspeed Insight helps districts review engagement, license use, and privacy information when evaluating their digital resource portfolio.

Application activity is useful only within the coverage of the configured collection. Technology, curriculum, and purchasing teams connect usage evidence with licensing, implementation goals, and the population actually represented. Observed activity is evidence about use within the collection’s coverage. It does not independently establish instructional effectiveness or the value of every license.