Cross-university platform portalShow a desktop notification when the AI TA finishes replying
Notify me when classmates post messages in the forum
Play an alert sound whenever there is a new notification
For use by each school's campus administrators (campus_admin) and campus viewers (campus_viewer): access and permissions, usage statistics dashboard, campus-level API Key (BYOK) settings, and administrator-assigned management.
How to get access, what the school admin console offers, and which data you can and cannot see.
The School Management Console is a self-service management interface provided by Uedu for institutional administrators at each school. After being assigned, school staff will receive one of the following two roles:
| role | System code | Permission |
|---|---|---|
| University affairs administrator | campus_admin | View usage statistics, set the institution-level API Key, assign other administrators from the same institution; for senior secondary/junior secondary schools, also manage the roster and create Courses |
| University affairs viewer | campus_viewer | Can only view information on each page; cannot add or modify any settings |
The authority of campus administrators is limited to their own university; platform administrators are the operations role on the Uedu platform side and can assign campus administrators for any university. In this manual, "administrator" refers to campus administrators unless otherwise stated.
Campus administrators and campus viewers are mandatory 2FA roles on the platform (the same as course instructors and TAs): accounts must enable two-step verification (primarily using a TOTP authenticator app). Users who have not enabled it will be directed to the setup page after logging in (https://uedu.tw/2fa/setup), and cannot use the platform until completed; while holding this role, they cannot disable 2FA themselves.
| Feature page | University | Senior secondary school / junior secondary school |
|---|---|---|
| Usage statistics dashboard | ✅ | ✅ |
| University-wide API Key (BYOK) | ✅ | ✅ |
| Administrator management | ✅ | ✅ |
| Student roster management | — | ✅ |
| Quick course creation (108 Curriculum integration) | — | ✅ |
In both channels, activation is ultimately via 'accept invitation + sign responsibility statement' (the account itself does not need teacher status):
https://uedu.tw/school-admin/, click “Apply to become a school administrator”, fill in your job title and application description, and submit it to the platform administrator for review; once approved, you will also be notified by invitation emailJust remember the admin overview https://uedu.tw/school-admin/: after signing in, the system will automatically redirect you to the school you manage (if you manage multiple schools, a list will be shown for selection). The URL for each school's console is https://uedu.tw/school-admin/{school-code}/, for example National Sun Yat-sen University is https://uedu.tw/school-admin/nsysu/. Once inside:
You can also enter each feature page directly via its URL:
| Feature | URL |
|---|---|
| Usage statistics dashboard | https://uedu.tw/school-admin/{school code}/stats |
| University-wide API Key | https://uedu.tw/school-admin/{school code}/api-keys |
| Administrator management | https://uedu.tw/school-admin/{school code}/admins |
| Audit log (school administrators only) | https://uedu.tw/school-admin/{school code}/audit |
| Student roster (K-12) | https://uedu.tw/school-admin/{school code}/roster |
| Quick course creation (K-12) | https://uedu.tw/school-admin/{school code}/courses |
Each feature page has a shared tab bar at the top (Student roster / Quick course creation / Administrator / API Key / Usage statistics); click to switch, with no need to remember URLs.
The dashboard shows the overall usage of your institution on the Uedu platform, and can be filtered by semester. All figures are aggregated statistics:
| Block | Content |
|---|---|
| Usage overview | Number of Courses, number of Instructors, number of Students, number of dialogues, number of messages |
| Course list | Name of each Course, Instructor, semester, number of Students, number of dialogues, number of messages |
| Course details | Select a single Course to view the trend in dialogue counts over the past 30 days, the distribution of Bloom levels, and a breakdown of storage usage |
| Distribution of cognitive levels | Statistics of the Bloom six levels in student questions across the university (remembering / understanding / applying / analysing / evaluating / creating) |
| Storage usage | The number and capacity of files of all types in the classroom, including recordings, screen recordings, teaching materials and dialogue attachments |
A CSV report can be downloaded from the bottom right for internal presentations or administrative reporting.
The dashboard provides only aggregated data, and does not provide individual Student lists, individual conversation content, or any personally identifiable detailed records. This is a platform privacy design principle, not a permissions issue.
What a school-level Key is, how to estimate costs and set it up, how the Key is protected, and what happens when its allowance runs out.
Uedu's AI dialogue feature requires calls to large language models (such as OpenAI), and the cost is calculated according to token usage. The platform uses a three-tier sequence to determine the API Key used by each Course:
| Priority | Layer | Description |
|---|---|---|
| 1 | Course-level Key | The Key entered by the Instructor on the Course Setup page only affects that Course |
| 2 | University-level Key | The Key set in this Console is shared by all courses across the university (when no course-level Key is set) |
| 3 | System quota | If neither is set, use the Higher Education Sprout Project or Uedu Public Welfare Token quota according to the institution's status |
After setting a school-level Key, your school can manage the AI usage budget independently, without being limited by the system quota, and it also makes internal expense reimbursement easier.
sk-; Azure also requires Endpoint and API Version)Obtain an OpenAI API Key: go to https://platform.openai.com/api-keys and create one (you need an OpenAI account and a linked payment method).
Please go to the OpenAI (or Azure) dashboard immediately to revoke the Key, then return to this page and paste in a new Key to overwrite it. The platform only stores the encrypted Key; revocation must be completed in the vendor dashboard.
'Your school Token usage' at the bottom of the page is categorised by Key level:
| Tags | Meaning |
|---|---|
school | Usage of the school-level key set on this page |
course | Usage of the Key set by the Instructor on the Course Setup page |
donation | Use your Uedu charity Token quota |
system／internal | Higher Education Sprout Project token usage |
We recommend also setting a monthly usage cap and alert emails in the OpenAI dashboard (Settings → Limits) as a second layer of protection; the usage table on the Uedu side can be used as the basis for reconciliation.
The "Administrators" page lists all the academic administrators and academic reviewers currently at your institution. New members are added by invitation only: their permissions take effect only after they accept the invitation and sign the responsibility statement.
The responsibility statement sets out the scope of the role's authority, the boundaries of data use (for university affairs only, not for individual instructor performance appraisal), Key custody responsibilities and audit methods. Two points to note:
Campus administrators can view university-wide usage statistics and set API Keys that affect the whole university. Please assign them only to official staff responsible within the university, and remember to remove them when there is a change of personnel.
This function is only available for senior high / junior high; university accounts cannot see these two tabs:
When teachers on campus encounter Uedu-related issues, they usually first consult the campus administrator. This chapter provides triage principles and reply templates ready for direct use.
| Type | Processing method |
|---|---|
| Course opening, Student enrolment, funding attribution | Campus administrators may reply directly (see the template below) |
| Claim Course, in-course settings (code, visibility, TA, self-provided Key) | Must be handled by the teacher personally; the school administrator cannot do this on your behalf. Please provide the path and complete the rest yourself. |
| Unable to log in to account, recognition review timed out and not approved, system error | Referral platform (footer feedback mechanism or platform contact point) |
A university Course is opened by the Instructor personally claiming it: the claiming process is tied to verification of the Instructor's school e-mail account, and responsibility lies with the Instructor personally, so the campus administrator cannot handle it on their behalf, and review is also carried out by the platform (rather than the campus administrator). The following template can be copied directly into a reply:
Dear Instructor:
Uedu courses are opened by the teaching instructor themself claiming the course, which takes about 3 minutes:
1. Log in to uedu.tw with your account and go to https://uedu.tw/teacher-claim/
2. Search for the course you teach by semester and click "Claim"
3. The system will send a 6-digit verification code to your school email address (valid for 15 minutes); after verification, submit the application
4. Once approved by the platform, you will be notified by email; the course will then appear in "My Courses" and all teaching tools will be enabled
If you cannot find your course (for example, a newly created course), please go to https://uedu.tw/create-course/ to apply for creation; it will also be opened after platform approval.
You can check the application progress at any time at https://uedu.tw/teacher-claim/my-applications.
School administrators in K-12 schools can use the console to “create courses quickly” and batch-create courses on behalf of teachers (108 Curriculum integration) without going through the claim process; the claim process is mainly for universities.
| Instructor asks | Reply key points |
|---|---|
| How do students join my course? | Please ask teachers to provide students with the Course Code (6 digits) or the course link on the Course page; for private courses, teachers may also review join requests on a case-by-case basis. |
| Do you have to pay for AI conversations? Who pays? | According to our school’s situation: where a school-level Key has been set, the school bears the cost; where none has been set, Uedu’s public-interest Token quota currently supports this (fundraising in progress; at this stage, the Uedu platform is absorbing the cost itself). Free for Students in all cases |
| I want to use my own API Key | Yes; please ask the Instructor to set it in the "Own API Key" section on the Course Management page. The Course-level Key takes priority over the school-level Key; the course cost will then be charged to the Instructor's Key |
| Course code, visibility, how are TAs set up? | All handled by the teacher on the Course Management page; the university administrator cannot see them and cannot change course settings on your behalf |
| Claim submission has been pending for a long time with no response | Please first check the status at /teacher-claim/my-applications; if there is still no result, please refer it to the platform for handling |
The first half of this chapter covers troubleshooting for console operations; the second half covers the questions schools ask most often. The second half is also published on the School FAQs page and can be forwarded directly to the relevant school unit.
| Question | Processing method |
|---|---|
| Entering the console shows 'Insufficient permissions' (403) | Confirm that you are signed in with the assigned Uedu account; if you have not yet been assigned one, please contact your school's academic affairs administrator or platform administrator |
| University account denied access to the roster / course creation page | Normal situation; these two pages are exclusive features for senior high school / junior high school |
| Cannot see the “Add API Key” section | Your role is campus_viewer, and you can only view; please contact the campus administrator to adjust your role |
| Test connection failed | Confirm the Key is pasted in full (with no extra spaces) and that the vendor account quota has not been exhausted; for Azure, also confirm the Endpoint and API Version are correct |
| After setting the school-level Key, this course is still billed against other quota | This Course's Instructor may have set a Course-level Key (which takes priority over the school-level one); the course category in the rubric can corroborate this |
| No data for this semester on the dashboard | Your institution has no course usage records for that semester; please select another semester |
| Did not receive the invitation email or has the invitation expired | Please ensure the other party logs in with the account corresponding to the invited email at https://uedu.tw/school-admin/; the landing page will list pending invitations. If expired, please send it again |
| In the console, you are directed to the "Declaration of Responsibility" signing page | Normal mechanism: when the declaration terms are updated (or the current version has not yet been signed), you must complete the signature before continuing to use |
| You are redirected to the "Two-step Verification Setup" page after logging in | Normal mechanism: institutional administrators are a mandatory 2FA role and must complete TOTP setup before using the platform; while holding this role, 2FA cannot be disabled |
Which organisation runs Uedu?
Uedu is independently developed and operated by Assistant Professor Chia-Kai Chang. It is an inter-school teaching platform and does not belong to any single school. All schools use it under the same terms; a school's dedicated entry point shows only the school name in text and does not use any school's emblem.
Will the platform be commercialised or show adverts?
No. Uedu is a teaching platform for research purposes and has no advertising.
Does the school need to purchase anything or sign a contract with the platform?
No purchase is required, and the platform does not charge schools or students any fees. Schools do not need to sign a contract with the platform; however, teachers and TAs who will access student data must each sign a data protection undertaking, published in full at uedu.tw/governance/agreements.
What costs might the school need to pay?
The only possible cost is if the school chooses to use its own OpenAI key (BYOK), in which case the API usage fees are paid directly to OpenAI. The platform does not handle the payment. As a budget estimate, you may conservatively allow around US$1 per student per month; actual usage can be checked in the console at any time.
What should the school do if it no longer wants to pay AI costs?
Your school coordinator can simply deactivate or remove the school-level API Key in the console; there is no need to notify the platform. After it is deactivated, your school's courses will use the credit provided by the platform. That credit is limited, and AI conversations will pause when it runs out.
Why are our school's courses already on the platform? Where does the data come from?
Course names, teaching staff and syllabuses are taken from the school's publicly available timetable information in its course selection system, so that teachers can quickly claim their courses. The platform does not contain teachers' teaching materials; after a teacher claims a course, it automatically becomes private, and teaching materials uploaded by the teacher are visible only to the students in that course.
What settings does the school need to make?
Almost none. Teachers claim courses and set AI teaching assistants with their own accounts; the school does not need to handle any additional administrative process. The school's dedicated URL is also configured by the platform side. The designated staff member only needs to check usage statistics as required and decide whether to set a school-level API Key.
How do students join a course? Do they need a school account?
Teachers give students the course code or course link, and students can join after logging in; teachers can also paste a list of student IDs taking the course. Student registration is not limited to school email addresses; any email address may be used.
Will usage statistics be used to assess teachers?
No. Before joining the console, the designated staff member must sign the statement of responsibilities, undertaking to use the statistics only for school administration purposes (for example, resource planning and performance reporting), and not for evaluating individual teachers' performance. Whether to use Uedu and how to use it is decided by the teacher.
What happens to courses and student data if a teacher leaves or transfers school?
Courses and student data follow the teacher's account and will not be transferred to the school because the teacher changes institution. When using and exporting these data, the teacher must comply with the data protection undertaking and export consent rules: only student data that has been consented to and not withdrawn may be exported; exports are enforced by the system; destruction must be recorded; no new export may be carried out once the destruction record is overdue.
Where is the data stored? Will it be used to train AI?
Platform data is stored on servers in Taiwan. AI conversations are sent to OpenAI (USA) for processing; according to the OpenAI API usage terms, this data will not be used to train models. Platform governance is based on whichever is stricter between the EU GDPR and Taiwan's Personal Data Protection Act, and the relevant documents are published at uedu.tw/governance.
Can the school see or export students' data?
The school can only see aggregated usage statistics; it cannot see individual student lists, grades or conversation content, and student data export is not provided on the school side. This is a deliberate design to protect students' personal privacy.
Can AI produce inappropriate content?
The platform uses models provided by OpenAI, with the model's own safety mechanisms acting as the safeguard. Teachers can also use the AI policy generator to set course-specific AI usage guidelines.
If a teacher conducts research on the platform, is separate IRB review required?
For research within the scope covered by the platform Umbrella IRB, no separate submission is required; research outside that scope must be applied for by the teacher. If the research belongs to a Ministry of Education or National Science and Technology Council funded project, it must follow the requirements of the competent authority, including those for research consent forms. The scope is explained at uedu.tw/governance/irb.
Will student participation in research affect grades?
No. After students sign the online research informed consent form, the teacher may export their conversation data; students who have not consented or have withdrawn consent will not appear in the exported data. Participation or non-participation in research does not affect students' course grades.
Can the school's single sign-on (SSO) be used?
School single sign-on is not currently supported. The platform provides password, Google, Apple, GitHub and Passkey sign-in methods.
Is there integration with Moodle or other learning management systems?
Not at present. Uedu can be used alongside the school's existing learning management system.
Which languages does the interface support? Is there an app?
The full site interface supports 16 languages, including the school admin console, and users can switch languages on the page. There is also an iOS app, UeduPAD.
What happens when the designated staff member changes?
The current designated staff member can first invite a new designated staff member to join, then use "Leave administration" on the console to step down; the rights will end immediately.
Who should we contact if there is a problem?
Please use the feedback mechanism in the website footer, or contact the platform via "Support and messages" after logging in.
/school-admin/{school code}/audit)If you encounter any problems with the operation that are not covered in this manual, please contact us via the feedback mechanism or contact window in the platform footer.