Arabic LMS for NGOs in Syria: Access and User Management

It is the first morning of a new training cycle, and the learning officer in an NGO programme office in Syria is answering messages instead of training. A field assistant cannot receive her sign-in email because her work mailbox has not been created yet. Two team leaders are sharing one login. A colleague who moved to another project last month still sees his old project’s courses. And three people lost their quiz answers when the connection dropped, and the new Arabic LMS logged them out.

None of these problems is about course content. They are about access: who can sign in, what each person can see, whether the learning record follows the person, and what happens when the connection fails. For NGO teams and teams implementing UN-funded programmes, where contracts are often tied to projects and staff, volunteers and consultants change frequently, these questions decide whether an Arabic LMS becomes the place where people learn or another system they avoid.

This article sets out practical tests for access and user management in an Arabic LMS: sign-in, permissions, the learning record and alternatives when connectivity drops. It is general guidance with non-sensitive examples. Your organization’s own policies, IT and data protection rules and donor requirements always take precedence.

Map Who Needs Access Before You Configure the Arabic LMS

Many access problems start because user groups were never defined. Before testing any learning management system, list everyone who will use the Arabic LMS and answer three questions for each group: how they sign in, who approves their account, and when their access ends.

• National staff on project-based contracts, whose access may need to end or move when a project closes.

• Volunteers, who may need only a few short courses and often have no work email address.

• Consultants and short-term staff, who need access for a defined period.

• Office focal points who coordinate training for their colleagues.

• Managers and HR staff who follow progress across teams.

Write the answers in a one-page access table and agree it with HR and IT. It becomes the reference for every test that follows, and for the Arabic LMS provider. One rule should apply to every group: each person has an individual account. Shared logins make the learning record meaningless and make it impossible to remove one person’s access without affecting others.

Testing Sign-In to the Arabic LMS

Sign-in is the first test an Arabic LMS must pass, and it is where many staff give up. Test it with real people from each user group, on the devices they actually use, rather than with the IT team on office computers.

Accessibility guidance offers a useful benchmark. Success Criterion 3.3.8, Accessible Authentication (Minimum), of the W3C’s Web Content Accessibility Guidelines (WCAG) 2.2 states that a cognitive function test, such as remembering a password or solving a puzzle, should not be required at any step of an authentication process unless an alternative or a supporting mechanism is available. The W3C’s explanation lists support for password managers as such a mechanism, and notes that users must at least be able to paste a verification code rather than retype it. Ask which WCAG version and level the Arabic LMS targets, then check sign-in yourself:

• First, sign in to the Arabic LMS with a work email, and with whatever a volunteer or new staff member actually has instead, such as a personal email or a mobile number.

• Password reset for someone whose email is unreliable or whose phone number has changed.

• Pasting a password or verification code, and saving the password in the phone’s password manager.

• Error messages in clear Arabic when the password is wrong, or the account is locked.

• Who can unlock an account, and how long that takes when the focal point is in the field.

Record each failure with the person’s group and device. A sign-in route to the Arabic LMS that works for head-office staff but fails for volunteers is a failed test, not a minor issue.

Setting Arabic LMS Permissions by Role, Office and Project

Permissions in an Arabic LMS should follow the way the organization actually works. In many programme offices, that means at least three dimensions: the person’s role, the office they belong to, and the project or programme they work on.

Define a small number of user roles, such as learner, office focal point, manager, HR, and administrator, and decide what each can see and do. Then test the boundaries with test accounts in the Arabic LMS:

• A focal point in one office can enroll and follow learners in that office only.

• A volunteer sees volunteer courses, not staff-only material such as internal finance procedures.

• A consultant’s access ends on the contract end date, either automatically or through a named person who closes it.

• A staff member who moves from one project to another loses the old project’s courses and gains the new ones, without losing completed records.

• Nobody outside the administrator role can change a completion or a score in the Arabic LMS.

Who can see training results, and in how much detail, is a reporting question as much as an access one. Our article on LMS training reports for humanitarian teams in Syria covers which data reports should be included and how to keep it to the minimum.

Keeping the Learning Record with the Person

In project-based work, people leave when a contract ends and sometimes return months later for a new project. If the Arabic LMS creates a new account each time, their earlier training disappears from view and courses are repeated unnecessarily. The learning record should follow the person, not the contract.

Agree on a unique identifier for each person, such as a staff number, and avoid using names as the key. Arabic names can be written in several Latin spellings, and the same person may appear as Mohammad, Mohamed, or Muhammad in different HR exports. Then test these situations in the Arabic LMS:

• Deactivate an account when a contract ends, reactivate it for a new contract, and confirm the earlier history is still there.

• Move a person between offices and confirm their record and certificates move with them.

• Correct the spelling of a name and confirm it does not create a second learner.

• Merge a duplicate account created by mistake, and check which record survives.

Also decide how long records of former staff and volunteers stay in the Arabic LMS, and who can see them, in line with your organization’s records and data protection policies.

When the Connection Drops: Testing Arabic LMS Access Alternatives

Interruptions to power or internet access are a practical condition to plan for in many field locations. The access question is not only whether a course loads, but what happens to a person signed in to the Arabic LMS when the connection disappears halfway through.

Session timeouts matter here. Success Criterion 2.2.5 of WCAG 2.2, Re-authenticating, is a Level AAA criterion: when an authenticated session expires, the user can continue the activity without loss of data after signing in again. The W3C explains that many sites end sessions after a period of inactivity for security reasons, and that this can cause problems for people who need more time. Even if you do not aim for Level AAA, it is a useful re-authentication test for an Arabic LMS used over weak connections:

• Start a quiz, disconnect, wait beyond the session timeout, reconnect, and sign in again. Are the answers still there?

• Close the browser or app in the middle of a module and reopen it on a weak mobile connection.

• If the provider says the Arabic LMS offers an app or an offline mode, download a course, switch to airplane mode, complete it, and reconnect. Check that the result reaches the right learner.

Then define what happens when online access is not possible at all: a printed version of the course, a session led by the focal point, or a short practice task confirmed by a supervisor. The completion must still reach the learning record later, under clear rules; our guide to recording eLearning task completion during connectivity interruptions sets them out. For volunteers with very limited time and data, see also lightweight eLearning for volunteer training in Syria.

A Hypothetical Example: An Arabic LMS Access Test in Hama

The following example is hypothetical and is included only to illustrate the method.

An NGO programme office in Hama plans to move its staff induction, finance procedures, and IT basics courses into an Arabic LMS. The learning officer invites eight people to a half-day access test: two staff members with work email, two who do not have it yet, one volunteer, one consultant, a team leader, and the office’s training focal point. Each uses their own phone, and two also try the shared office computer.

The test of the Arabic LMS finds four problems. Password reset depends on email, so the two newest staff members cannot recover their accounts alone. On one older phone, the verification code cannot be pasted, and retyping it takes longer than the code stays valid. The team leader’s role shows learners from every office, not only his own. And when the connection is cut during a quiz and the session expires, the answers are gone after signing in again.

The office sets up a reset procedure through the focal point while the provider confirms other options, asks for the team leader role to be limited by office, and asks whether quiz answers can be saved question by question. Until then, quizzes stay short, and a printed version is available. Two weeks later, the same test is repeated with different people before the Arabic LMS is opened to the whole office.

Summary

Access decides whether an Arabic LMS works for NGO teams in Syria before any course is opened. Map every user group, give each person an individual account, and test sign-in with the people and devices you actually have, including those without a work email.

Set permissions by role, office, and project; keep the learning record with the person when contracts end and restart, and test what happens when the connection drops. A half-day access test with a handful of real users will tell you more about an Arabic LMS than any demonstration.

Click here. If your organization is preparing to set up or test access in an Arabic LMS, the SkillUp MENA team can talk through your requirements with you.