itslearning · Sanoma Learning · 2026

Making course permissions clear for every teacher

A redesign of the course permission system in itslearning, a learning platform used by schools. Rebuilt to WCAG 2.2, entirely from the component library, and live in German schools since February 2026.

Role

UX/UI Designer — Web, Design System

Team

Product owner, developers, UX writer, QA

Company

Sanoma Learning

Released

February 2026 · German Development Project

itslearning · Sanoma Learning · 2026

Making course permissions clear for every teacher

A redesign of the course permission system in itslearning, a learning platform used by schools. Rebuilt to WCAG 2.2, entirely from the component library, and live in German schools since February 2026.

Role

UX/UI Designer — Web, Design System

Team

Product owner, developers, UX writer, QA

Company

Sanoma Learning

Released

February 2026 · German Development Project

itslearning · Sanoma Learning · 2026

Making course permissions clear for every teacher

A redesign of the course permission system in itslearning, a learning platform used by schools. Rebuilt to WCAG 2.2, entirely from the component library, and live in German schools since February 2026.

Role

UX/UI Designer — Web, Design System

Team

Product owner, developers, UX writer, QA

Company

Sanoma Learning

Released

February 2026 · German Development Project

Two itslearning screens: the Assign additional permissions page under the permissions page for a course, with a table of roles and Allowed or Denied badges
Two itslearning screens: the Assign additional permissions page under the permissions page for a course, with a table of roles and Allowed or Denied badges

In short

Problem

Teachers couldn’t tell who had what access in a course. The old interface was cluttered, explained its statuses poorly and failed WCAG 2.2.

What I did

Reworked the permissions page with a separate flow for adding permissions, added a tab with every participant’s actual access, and rebuilt it all from the component library.

Result

Released in February 2026 and used in German schools as part of the German Development Project.

In short

Problem

Teachers couldn’t tell who had what access in a course. The old interface was cluttered, explained its statuses poorly and failed WCAG 2.2.

What I did

Reworked the permissions page with a separate flow for adding permissions, added a tab with every participant’s actual access, and rebuilt it all from the component library.

Result

Released in February 2026 and used in German schools as part of the German Development Project.

In short

Problem

Teachers couldn’t tell who had what access in a course. The old interface was cluttered, explained its statuses poorly and failed WCAG 2.2.

What I did

Reworked the permissions page with a separate flow for adding permissions, added a tab with every participant’s actual access, and rebuilt it all from the component library.

Result

Released in February 2026 and used in German schools as part of the German Development Project.

01 · Context

Who can see and change what

Every itslearning course has a permission system: it decides who can view resources and who can edit or manage content. Teachers and course administrators manage it. The work shipped under the German Development Project, a joint programme of four German states and itslearning to advance digital education — a live product with real users inside a government initiative.

01 · Context

Who can see and change what

Every itslearning course has a permission system: it decides who can view resources and who can edit or manage content. Teachers and course administrators manage it. The work shipped under the German Development Project, a joint programme of four German states and itslearning to advance digital education — a live product with real users inside a government initiative.

01 · Context

Who can see and change what

Every itslearning course has a permission system: it decides who can view resources and who can edit or manage content. Teachers and course administrators manage it. The work shipped under the German Development Project, a joint programme of four German states and itslearning to advance digital education — a live product with real users inside a government initiative.

02 · Goals

Three goals, set from the start

01

Clarity

Make selecting and assigning permissions as clear as possible.

02

Accessibility

Bring the interface up to WCAG 2.2 — as a goal, not a final check.

03

One component library

Build everything from the library for consistency and easier maintenance.

02 · Goals

Three goals, set from the start

01

Clarity

Make selecting and assigning permissions as clear as possible.

02

Accessibility

Bring the interface up to WCAG 2.2 — as a goal, not a final check.

03

One component library

Build everything from the library for consistency and easier maintenance.

02 · Goals

Three goals, set from the start

01

Clarity

Make selecting and assigning permissions as clear as possible.

02

Accessibility

Bring the interface up to WCAG 2.2 — as a goal, not a final check.

03

One component library

Build everything from the library for consistency and easier maintenance.

03 · Starting point

Five problems with the old interface

Confusing process

Assigning and editing permissions was cluttered, and the logic wasn’t obvious.

Failed WCAG 2.2

The old version didn’t meet current accessibility requirements.

Statuses were hard to read

The interface did explain each status, but poorly — the explanations were easy to miss and hard to understand.

User vs group

One person could appear as an individual and as a group member, hiding their real access.

Outdated components

Not built from the current library — harder to maintain and inconsistent.

03 · Starting point

Five problems with the old interface

Confusing process

Assigning and editing permissions was cluttered, and the logic wasn’t obvious.

Failed WCAG 2.2

The old version didn’t meet current accessibility requirements.

Statuses were hard to read

The interface did explain each status, but poorly — the explanations were easy to miss and hard to understand.

User vs group

One person could appear as an individual and as a group member, hiding their real access.

Outdated components

Not built from the current library — harder to maintain and inconsistent.

03 · Starting point

Five problems with the old interface

Confusing process

Assigning and editing permissions was cluttered, and the logic wasn’t obvious.

Failed WCAG 2.2

The old version didn’t meet current accessibility requirements.

Statuses were hard to read

The interface did explain each status, but poorly — the explanations were easy to miss and hard to understand.

User vs group

One person could appear as an individual and as a group member, hiding their real access.

Outdated components

Not built from the current library — harder to maintain and inconsistent.

Old itslearning permissions screen: a table of roles with coloured status dots and a text explaining the permissions below

Old interface — permissions list

Old itslearning permissions screen: a table of roles with coloured status dots and explanations of the permissions below

Old interface — editing a permission

Old itslearning permissions screen: a table of roles with coloured status dots and a text explaining the permissions below

Old interface — permissions list

Old itslearning permissions screen: a table of roles with coloured status dots and explanations of the permissions below

Old interface — editing a permission

Old itslearning permissions screen: a table of roles with coloured status dots and a text explaining the permissions below

Old interface — permissions list

Old itslearning permissions screen: a table of roles with coloured status dots and explanations of the permissions below

Old interface — editing a permission

04 · Approach

Expert review, then a flow the developers signed off

There was no separate user research on this project, so I based decisions on an expert review against usability heuristics, WCAG 2.2 requirements and technical constraints. I rebuilt the flow around a simple rule — each step does one thing and shows what it changes — and agreed it with the developers before detailed design. That took the risk of late rework off the table.

04 · Approach

Expert review, then a flow the developers signed off

There was no separate user research on this project, so I based decisions on an expert review against usability heuristics, WCAG 2.2 requirements and technical constraints. I rebuilt the flow around a simple rule — each step does one thing and shows what it changes — and agreed it with the developers before detailed design. That took the risk of late rework off the table.

04 · Approach

Expert review, then a flow the developers signed off

There was no separate user research on this project, so I based decisions on an expert review against usability heuristics, WCAG 2.2 requirements and technical constraints. I rebuilt the flow around a simple rule — each step does one thing and shows what it changes — and agreed it with the developers before detailed design. That took the risk of late rework off the table.

User flow: open the permission page, which first inherits the parent folder’s permissions. Customise to make it editable, or reset back to the parent; the per-participant view is a tab next to it. From the editable page, choose mass edit (overwrite existing permissions), add new (assign additional permissions page) or single edit (edit permissions for a participant or group). If members and their groups have conflicting rights, the page shows a conflict info banner; if not, a save confirmation banner. Finally, the permissions are applied to the resource.

New user flow

User flow: open the permission page, which first inherits the parent folder’s permissions. Customise to make it editable, or reset back to the parent; the per-participant view is a tab next to it. From the editable page, choose mass edit (overwrite existing permissions), add new (assign additional permissions page) or single edit (edit permissions for a participant or group). If members and their groups have conflicting rights, the page shows a conflict info banner; if not, a save confirmation banner. Finally, the permissions are applied to the resource.

New user flow

05 · Key decisions

Decision 01

A clearer permissions page

Permissions already had a page, but working with it was confusing. I rebuilt it around clear entry points — a separate page for adding permissions and two ways to edit existing ones. The process became easier to follow and accessible, including with a keyboard and a screen reader.

05 · Key decisions

Decision 01

A clearer permissions page

Permissions already had a page, but working with it was confusing. I rebuilt it around clear entry points — a separate page for adding permissions and two ways to edit existing ones. The process became easier to follow and accessible, including with a keyboard and a screen reader.

05 · Key decisions

Decision 01

A clearer permissions page

Permissions already had a page, but working with it was confusing. I rebuilt it around clear entry points — a separate page for adding permissions and two ways to edit existing ones. The process became easier to follow and accessible, including with a keyboard and a screen reader.

Reworked permissions page in a course: a banner explaining how permissions work above the list of roles and their permissions

The reworked permissions page

Reworked permissions page in a course: a banner explaining how permissions work above the list of roles and their permissions

The reworked permissions page

Decision 02

Two ways to edit

An Actions menu for bulk changes on selected rows, and a pencil Edit button for a quick change to a single entry.

Decision 02

Two ways to edit

An Actions menu for bulk changes on selected rows, and a pencil Edit button for a quick change to a single entry.

Decision 02

Two ways to edit

An Actions menu for bulk changes on selected rows, and a pencil Edit button for a quick change to a single entry.

Decision 03

Adding permissions on its own page

Adding new permissions moved to a separate page, “Assign additional permissions”. Every permission there is labelled and explained, and students and groups are picked from one clear, searchable list — so a teacher sees exactly what they’re granting and to whom. In the old interface, adding permissions was part of a cluttered flow.

Decision 03

Adding permissions on its own page

Adding new permissions moved to a separate page, “Assign additional permissions”. Every permission there is labelled and explained, and students and groups are picked from one clear, searchable list — so a teacher sees exactly what they’re granting and to whom. In the old interface, adding permissions was part of a cluttered flow.

Decision 03

Adding permissions on its own page

Adding new permissions moved to a separate page, “Assign additional permissions”. Every permission there is labelled and explained, and students and groups are picked from one clear, searchable list — so a teacher sees exactly what they’re granting and to whom. In the old interface, adding permissions was part of a cluttered flow.

Assign additional permissions page: a picker for participants and groups and a list of permissions, each with a short description

Assigning additional permissions

Assign additional permissions page: a picker for participants and groups and a list of permissions, each with a short description

Assigning additional permissions

Decision 04

Statuses that are easy to understand

Full control, Edit, Write, Evaluate, Participate, Read — the logic behind the statuses stayed the same. The old interface did explain them, but in a way that was easy to miss and hard to follow. Together with the UX writer, I rewrote the label and description of every status, so a teacher understands what each one allows at a glance.

Decision 04

Statuses that are easy to understand

Full control, Edit, Write, Evaluate, Participate, Read — the logic behind the statuses stayed the same. The old interface did explain them, but in a way that was easy to miss and hard to follow. Together with the UX writer, I rewrote the label and description of every status, so a teacher understands what each one allows at a glance.

Decision 04

Statuses that are easy to understand

Full control, Edit, Write, Evaluate, Participate, Read — the logic behind the statuses stayed the same. The old interface did explain them, but in a way that was easy to miss and hard to follow. Together with the UX writer, I rewrote the label and description of every status, so a teacher understands what each one allows at a glance.

Decision 05

Banners for how it works and for conflicts

Banners explain how permissions work and flag conflicts — when a participant has extra access on top of their base level.

Decision 05

Banners for how it works and for conflicts

Banners explain how permissions work and flag conflicts — when a participant has extra access on top of their base level.

Decision 05

Banners for how it works and for conflicts

Banners explain how permissions work and flag conflicts — when a participant has extra access on top of their base level.

Permissions list with a conflict banner explaining that the most permissive rule wins when a participant is in several groups

Explanatory and conflict banners

Permissions list with a conflict banner explaining that the most permissive rule wins when a participant is in several groups

Explanatory and conflict banners

Decision 06

One tab that shows actual access

The same person could be an individual and a member of several groups. The “Permissions per participant” tab lists every student and colleague with their actual access — the sum of everything they get on the Permissions tab: their own permissions plus those of every group they belong to.

Decision 06

One tab that shows actual access

The same person could be an individual and a member of several groups. The “Permissions per participant” tab lists every student and colleague with their actual access — the sum of everything they get on the Permissions tab: their own permissions plus those of every group they belong to.

Decision 06

One tab that shows actual access

The same person could be an individual and a member of several groups. The “Permissions per participant” tab lists every student and colleague with their actual access — the sum of everything they get on the Permissions tab: their own permissions plus those of every group they belong to.

Permissions per participant tab: each student and colleague with Allowed or Denied for every permission

Permissions per participant

Permissions per participant tab: each student and colleague with Allowed or Denied for every permission

Permissions per participant

See it in use

A walkthrough from the official itslearning tutorial

This is how teachers see the feature today — in itslearning’s own video guide for schools.

See it in use

A walkthrough from the official itslearning tutorial

This is how teachers see the feature today — in itslearning’s own video guide for schools.

See it in use

A walkthrough from the official itslearning tutorial

This is how teachers see the feature today — in itslearning’s own video guide for schools.

Course permissions in itslearning

Official itslearning tutorial

Course permissions in itslearning

Official itslearning tutorial

06 · Accessibility

Accessibility was a goal, not a final check

2.1.1 · 4.1.2

Keyboard and screen readers

Logical tab order and screen-reader support across the whole flow, including assigning permissions.

1.3.1 · 4.1.2

Text labels for every status

Each status has a label that assistive technology can announce.

1.4.1

Not by colour alone

Statuses always include text, so they work for people with colour-vision deficiencies.

2.4.7 · 3.2.4

Accessible library components

Visible focus and consistent behaviour came with the components.

06 · Accessibility

Accessibility was a goal, not a final check

2.1.1 · 4.1.2

Keyboard and screen readers

Logical tab order and screen-reader support across the whole flow, including assigning permissions.

1.3.1 · 4.1.2

Text labels for every status

Each status has a label that assistive technology can announce.

1.4.1

Not by colour alone

Statuses always include text, so they work for people with colour-vision deficiencies.

2.4.7 · 3.2.4

Accessible library components

Visible focus and consistent behaviour came with the components.

06 · Accessibility

Accessibility was a goal, not a final check

2.1.1 · 4.1.2

Keyboard and screen readers

Logical tab order and screen-reader support across the whole flow, including assigning permissions.

1.3.1 · 4.1.2

Text labels for every status

Each status has a label that assistive technology can announce.

1.4.1

Not by colour alone

Statuses always include text, so they work for people with colour-vision deficiencies.

2.4.7 · 3.2.4

Accessible library components

Visible focus and consistent behaviour came with the components.

07 · Result

Live in schools since February 2026

The new permission system was released in February 2026 and is used in German schools as part of the German Development Project. To see how well the redesign works, I’d look at these metrics:

07 · Result

Live in schools since February 2026

The new permission system was released in February 2026 and is used in German schools as part of the German Development Project. To see how well the redesign works, I’d look at these metrics:

07 · Result

Live in schools since February 2026

The new permission system was released in February 2026 and is used in German schools as part of the German Development Project. To see how well the redesign works, I’d look at these metrics:

What I’d measure next

Time to assign correctly

How long it takes to give the right person the right access.

Support requests

Number of tickets about course access.

Task success with assistive tech

For keyboard and screen-reader users.

What I’d measure next

Time to assign correctly

How long it takes to give the right person the right access.

Support requests

Number of tickets about course access.

Task success with assistive tech

For keyboard and screen-reader users.

What I’d measure next

Time to assign correctly

How long it takes to give the right person the right access.

Support requests

Number of tickets about course access.

Task success with assistive tech

For keyboard and screen-reader users.

© 2026 Dzmitry Shkutnik

Designed in Figma · Built in Framer