AI agents for university administration
Nibras agents work inside your systems. Each one reads a request, applies your own regulations, closes what is routine, and puts the decisions that need a person in front of the person who owns them — in Arabic and English.
Example run from a pilot-sized office. Not live data.
The agents
Each agent learns one office: its work, its regulations, its systems. You draw the line between what it closes on its own and what it sends to a member of staff.
How it starts
This does not need a year-long programme. The agent starts read-only and earns each permission in stages, with your sign-off at every step.
Weeks 1–2
We connect the agent to your student system, LMS and mail with the access your IT team grants. In this stage it reads and drafts only; it changes nothing.
Weeks 3–4
You upload the academic regulations, the catalogue, the fee schedule and your approved templates. Then you draw the line: what the agent closes, and what needs a human signature.
First term
The agent works one office for a full term and logs every action with the clause it relied on. When the team trusts it, you add the next office.
The terms
Nibras runs on Microsoft Azure in the UAE North region, and each university gets its own isolated environment. Your data is never used to train a model.
Agents read and write formal Arabic and English, reply to each student or colleague in the language they wrote in, and keep your official letter formats intact.
Admissions, grades, discipline and hiring always go to a member of staff. You decide what else needs an approval before it moves.
Every action is logged with its reason, the clause behind it and who saw it. Your team can review it, reverse it, and use it as evidence at accreditation review.
Request a pilot
Nothing here disappears into a form. Make your choices, then copy the finished request and send it to us by email. We come back with a pilot plan for one office.
Nibras means lamp