Print Permanent link to this page

The EdTech partnership agreement is concluded between the Federal Ministry of Education, Science and Research (BMBWF) and a partner organization that offers an application for schools. The EdTech partnership agreement primarily covers the following aspects:

  1. Data processing agreement
  2. Single Sign On - Entity categories
  3. Interfaces

Attention: The EdTech agreement does not represent a commission, licensing or usage rights must be obtained by schools or school administrators themselves.

Onboarding of EdTech partners

The onboarding process defines the steps required for partners to link applications with the education portal. with the education portal. This enables the use of single sign-on and the use of the education portal's interfaces, such as the widget interface. education portal, such as the widget interface.

The education portal has a quality assurance environment (Q environment) in which no real personal data is processed. are processed. Technical integration in this Q environment can therefore begin before the agreement is signed. is signed. The roll-out in the integration environment (I environment) or the production environment (P environment) requires a concluded EdTech agreement.

Step 1: Establishing contact

EdTech partners are requested to contact the Pres/14 department at support@bildung.gv.at to get in touch. There is technical documentation in a GitHub repository that can be accessed by invitation. When contacting us, please name your own technical contacts who should receive such an invitation.

In the course of responding to the request, the EdTech partner will be given specific contact persons for further processing. will be provided.

Step 2: Initial filling of the documents

EdTech partners are asked to complete the documents, whereby the documentation referenced in step 1 is useful. These documents are*):

  • Partnership agreement [docx] [odt]
    The partnership agreement regulates the conditions under which the BMBWF and the respective partners cooperate with regard to the education portal.
  • Appendix A: AVV [docx] [odt]
    Appendix A of the partnership agreement is the data processing agreement (AVV), which must be signed separately, which must be in place before data from the education portal can be passed on to the partner.
  • Appendix B-E: Interfaces, widgets and SSO [docx] [odt]
    In Appendix B, the partner describes its own application and the purposes for which the data is processed. It is agreed with the BMBWF which of the standard interfaces offered (e.g. retrieval of master data, triggering notifications to legal guardians, searching content repositories, sending official delivery, ...) will be available for this application. This selection must be made in accordance with the described purposes of data processing and follow the principles of data minimization. Furthermore, a partner may only use the data from these interfaces for the purposes specified in the partnership agreement.
    At the time of signing, it is not necessary that an application supports all agreed interfaces. The operationalization of the interfaces is possible at any time by the partner.
    Appendix C defines which widgets are intended for a specific application. As with the standard interfaces, these widgets are configured by the BMBWF and can be operationally set by the partner at a later date.
    Appendix D can be used to describe other interfaces that a partner would like to implement apart from the standard interfaces. Such interfaces must be provided by the respective partner as Moodle plugin. In this case, Appendix D regulates the permitted functional scope of these interfaces. Integration into the education portal is subject to a technical and legal review by the BMBWF.
    Appendix E specifies the extent to which the SSO token is enriched with personal data when logging in via the education portal to the third-party application.
*) These documents are currently only available in German.

Step 3: Review by the BMBWF

The EdTech partners send the documents, completed to the best of their knowledge, to their contact persons. The content is adapted by mutual agreement and signed by the EdTech partner after approval by the BMBWF.

Step 4: Confirmation by the BMBWF

The documents signed by the EdTech partner are confirmed once again by the BMBWF in the file. The countersigned documents are returned to the EdTech partner.