AccessPoint Learning Studio

AccessPoint Learning adds lessons of your organization's own to learning paths. A module is a short lesson of up to twenty steps — a page to read, an image to study, a policy to open and acknowledge, a training case to practice, a real first task, a conversation with a mentor, a private reflection. You write modules in the Studio.

Open the Studio from the Training hub → Learning content → Studio, or from Settings → Training → AccessPoint Learning → Open the Studio. Authors (Author learning content) and training leads (Manage training) see it. Its Help opens this page.

The Studio works in your real work only; in Lab mode it is refused.

The Studio's Tabs

What Needs the AccessPoint Learning Module

Learning itself is part of the core product: My learning, the module player, the jurisdiction packs' modules and learning paths, completion records, reminders, the completion-records export, assigning a learning path by hand and the Coach tab all work without it.

Writing needs the AccessPoint Learning module: the Modules, Learning paths, Assets and Translations tabs, files, the page editor, translations, your blocks on pack modules and audience rules. The Quality, Glossary, Obligations and Lab scenarios tabs come with the module too. Without it, the writing tabs say Modules, learning paths, assets and translations are available with the AccessPoint Learning module, and the Studio opens on its Coach tab.

• AccessPoint for Microsoft 365 — every marketplace plan includes the module.
• Hosted AccessPoint — it is the AccessPoint Learning add-on. An administrator adds it under Settings → Subscription. The 30-day trial includes it; on the Free plan it is read-only, and the modules your organization wrote stay as they were.

If a licence later leaves the module out, nothing is deleted: published modules stay available to the people who take them, and writing comes back when the module is licensed again.

Starting a Module

1. On Modules, select New module.
2. Choose what to start from: Role primer (what a role does, how your organization decides, a tour, a first real task and a reflection), Decision lesson, Policy acknowledgment, Annual refresher or Blank module.
3. Give it a code (unique in your organization), a title, a level (Foundation, Practitioner or Advanced), the estimated minutes and its default language.
4. Under About the module, write its summary and up to ten objectives, one per line — what the learner will be able to do.

The Decision lesson, Policy acknowledgment and Annual refresher templates also hold a Check step (and Decision lesson a Decide step) for you to fill in.

Steps

A module has up to twenty steps. Add step offers the kinds below. Each step's Move up, Move down, Duplicate and Delete are in the step outline, and its Learners must do this step to finish the module box makes it required (the default) or optional. Each kind of step is done in its own way, and only AccessPoint decides the steps it can check.

The learner cannot tick an Exercise, Do or Check step themselves.

A step of a kind your version of AccessPoint does not know (for example from a newer pack) opens read-only, is kept exactly as it is when you save, and stops the module from being published until you delete it.

Exercise Steps

An Exercise step names a training scenario and, optionally, an introduction and a model answer — what a good case looks like, step by step, in your organization's words.

• Learners see the model answer only once AccessPoint sees their training case finished by its guide, beside a link to their own case in Lab mode. The training case's guide shows it too.
• The model answer is translated with the module's other texts. Like a Decide step's case, it must be fiction: publishing refuses real-looking e-mail addresses, telephone numbers and identifiers in it.
• The Exercise editor lists what the training case checks, step by step.
• The scenario list offers every practice scenario your organization has, including a training provider's private pack exercises, marked Lab only. In their real work, learners see nothing of such an exercise but its title and Open in Lab mode.
• A scenario that is switched off, or needs configuration your organization lacks, is marked not available now and stops the module from being published.

Writing a Page

A Read step's page is written in the page editor, inside the Studio: headings (levels 2 to 4), paragraphs, bulleted and numbered lists, quotes, callouts, tables with a header row, images, links to files and web links (https:// or mailto: only).

• Alt+F10 moves to the editor's toolbar and Escape back; Escape in the page moves on to the Studio.
• Pasting from Word keeps the structure (headings, lists, bold, italic, links) and drops everything else. A picture is never pasted: images and files are uploaded and chosen in the Studio.
• An image needs alternative text unless you mark it decorative.
• AccessPoint stores what you write as structured text, never as HTML.

Other long texts — a Look step's long description, a File step's summary — are written in the block editor used for coach notes.

Saving

The Studio saves your draft about four seconds after you stop typing. The line under the title says Saved at or Unsaved changes, with Save now if a save failed — your edits are kept.

If someone else saved the same draft meanwhile, the page turns read-only with Saved by at . This page is read-only until you reload it. and Reload. Nothing of yours is saved over their work. All modules saves before it goes back.

Images and Files

Images and files belong to one module. Upload them on the Assets tab, or from the page editor and the Look and File steps.

• Images can be PNG, JPEG, GIF or WebP, up to 10 MB each. Other files can be up to your document upload limit, with at most 200 per module.
• A web page (.html, .htm) is accepted and shown to learners only as a PDF, and an SVG image only as a PNG. AccessPoint converts them with scripts off and no network access, so a page's linked images and styles are not loaded, and an SVG's transparent areas turn white. The Studio says so when you upload one: put a page's pictures in the page itself, or upload them as files of their own. Where your AccessPoint does not run document conversion, a web page or an SVG is refused at upload.
• Programs, scripts, video and audio are refused. The original of a converted file is never shown to anyone.

Every file is scanned for malware like any upload. The Assets tab shows each file's type, size, scan result and the published versions that use it.

• You can open a file yourself only once its scan passes — clean, not scanned, or a failed scan acknowledged.
• A file that failed its scan needs Acknowledge the failed scan, with a reason, before it can be published. A malicious file blocks publishing until you remove it.
• A file a published version uses cannot be deleted. Learners can open a file only once a published version they take uses it.

Checks and Decisions

Writing a check. Add a Check step and select Add a question (up to ten). For each question:

1. Choose its kind — One right answer, Several right answers, True or false or Put in order.
2. Write the question and its options (up to ten), and tick The right answer (one, or several).
3. Optionally write Feedback on this option for any option. Learners see it after they answer, beside the right answer.
4. For Put in order, list the options in the right order with Move up and Move down. Learners see them shuffled and give each a number.

Set the Pass mark (80% by default) and Limit the attempts if you want a number (unlimited by default). Shuffle questions and options for each attempt is on by default. A check has no time limit. Questions, options and right answers are set while writing the module's default language; in another language you write their words.

Writing a decision. Add a Decide step and write the Scenario (a short case), The question, two to eight options (or none, when learners only write their reasons), The model answer's choice, whether learners may choose more than one, whether to ask for their reasons (not, optional or required, with what to ask), and the Model answer and its reasoning.

The case must be fiction. Check refuses an e-mail address outside the domains reserved for examples (example.com, example.org, example.net or .test), a telephone number outside the ranges kept for fiction (such as 555-0100 to 555-0199), and a number that passes a government identifier's checksum. Use made-up names.

How much of a check's results a lead sees is set under Settings → Training → AccessPoint Learning → Who sees check results (see Completion Records and Team Progress).

Checking and Previewing

Check lists what would stop the module from being published, and what only warns, each on its step, field and language. Selecting a finding takes you to the field.

• Errors include a missing title or required text, an image without alternative text, link words that are only the address or say "click here", a link that is not https://, a file still being scanned or converted, and a step kind that cannot be published.
• Warnings include a skipped heading level and a language not yet written.

After the first check, it runs again after every save. Preview as learner shows the module as a learner sees it, in any of your languages.

Translations

You write a module in its default language, and you can write any of your organization's other languages yourself: choose it in Writing in, and each field shows the default language's words under it.

The Translations tab lists, per module, each language's state — Original, Machine translation, Written by a person, Missing or Outdated (the default language changed after it was written) — and every text of a language beside the default language's, written in place.

Translate missing and Translate outdated translate one language at a time. They need AI Assist and your organization's automatic translation switched on — in AccessPoint for Microsoft 365, with Azure OpenAI deployed; in Hosted AccessPoint, with the AI Assist add-on.

• Machine translation changes only the words, never the structure, links or images. An image's alternative text and caption inside a page are words too, and are translated with the page.
• In a language a person wrote, Translate missing fills only the texts not written yet, each marked Machine translation, and never changes a text the person wrote. Translate outdated leaves such a language alone.
• Editing one text of a machine-translated language makes the language a person's, but only the texts you change become yours: every text you leave keeps its Machine translation mark.
• A language that is only partly written stops the module from being published, because a learner would see a mix of languages. A missing or outdated language only warns, and its learners see the whole module in the default language with a note saying so.

Publishing

People who hold Manage training publish. An author without it can check and preview but not publish.

1. Select Publish. AccessPoint checks the draft again.
2. Write What changed — a short note.
3. From the second version, choose whether it is a material change: ask everyone who completed an earlier version to review this one.

A published version never changes; your next edits are the next version's draft. A material change marks the completion records of earlier versions Review needed and opens a new cycle, due in 14 days, for the people who completed them (see Completion Records and Team Progress).

Publish Review

With Settings → Training → AccessPoint Learning → A second person approves each module before it is published switched on (off by default), Publish reads Send for approval. The draft waits (Waiting for approval) until someone else who manages training selects Approve and publish — never the person who sent it. The check runs again at approval. Changing a draft that waits for approval takes it back from review.

Copies, Browse, Retiring and Deleting

• Duplicate copies one of your modules. Make a copy turns a pack module into one of your own; the copy no longer receives the pack's updates. A copy starts as a draft with the same steps, texts, images and files. Each file is copied with its scan result, except that a malicious file is not copied (the check names it) and a failed scan's acknowledgement is not carried over — acknowledge the copy's file again.
• Open to Browse — when it is on, anyone in your organization can find the module under Browse in My learning and take it without being enrolled. It is off for your organization's own modules (and copies) until an author, or someone who manages training, switches it on. A jurisdiction pack's module comes as its pack ships it, and you may switch it off. A module that is not open is neither listed nor opened for someone it was not given to. People enrolled in a learning path that holds the module take it either way.
• Retire — a training lead retires a published module: people who started it can finish it, no new learning path item can name it, and it leaves Browse.
• Delete — a module that was never published can be deleted, with its draft and files.

Quality

The Quality tab shows how each module works for the people who take it, so you can fix a confusing question, a misleading option or a dead link. Choose a Module that has a published version, and a Version.

• Anonymous by construction. Every figure describes at least five learners of that version and never names anyone. With fewer, the tab says Too few to show. A learner's own words — a decision's reasons, a Reflect note — are never shown or counted.
• The module — how many learners, the share who completed the version, and the median attempts at its checks.
• Each question — the share right at the first attempt and at the latest attempt, and how many chose each option at their first attempt. A question most people get wrong at first, or an option nobody picks, is worth a second look.
• Each decision — how many chose each option, with the model answer's marked.
• Filters — Learners narrows to one learning path that lists the module; Period to the last 30 or 90 days or 12 months. A filter that leaves fewer than five learners, or leaves out fewer than five, shows Too few to show. There is no filter by person, audience rule or department.

Links. Once a week AccessPoint checks every public web address written into your modules, without downloading the page or sending anything about your organization or any person. The tab lists the dead ones — Not found, The site answered with an error, or No answer — with the step, the language and the day it first failed. A page behind a sign-in is counted as could not be confirmed, and a link to your private network is never requested. After fixing a link, Check now checks the module at once (at most once every ten minutes).

Languages. The tab also lists the languages your organization offers that the version has not been translated into, and those that are Outdated.

Glossary and Obligations

Glossary. Each term has its words and a short definition in each of your organization's languages. Terms from a jurisdiction pack are read-only, marked Pack: , and can be switched off; authors add, change and delete your organization's own. To mark a term in a page, select the words in the page editor, choose the Glossary term button, pick the term and select Mark the words. In the player, marked words have a dotted underline and open their definition when a learner moves to them, taps or clicks them.

Obligations are the training obligations your learning paths cover: a regime's syllabus items from a jurisdiction pack (read-only, but each can be switched off with Counted) and your own policy's training clauses. Authors read the list; people who manage training add, change and delete your own. A module names the obligations it covers under About the module → Obligation codes it covers, and a learning path in its own settings. The Obligation coverage subject in Report Studio shows which obligations your learning paths cover and how many people are certified, overdue or expired — never naming anyone.

Lab Scenarios: Your Organization's Own Scripts

Lab scenarios is where you decide what the people around a trainee say and do in Lab mode's practice cases and team simulations. Authors write scripts; training leads can read them.

Pick a scenario. Its people are listed — the requestor, a consulted third party, a complainant, the regulator's contact and the staff a trainee works with — each with who answers: the scenario's script, our script or not scripted.

Writing a Script

1. Select Write our script (or Edit our script) beside a person. Select Start from the scenario's script if you want to adapt it.
2. Choose Add what they answer for each part of their work — replies to letters, a response to a consultation, the regulator's steps, a search, decisions, advice, section answers, work, sign-off or opinions.
3. For each part, set When they answer — a number of minutes, hours or days of exercise time, or only when the lead releases an event that names them — and write its rounds in order. The first time the person is asked they answer with round 1, the second time round 2, and so on. Change the order with the numbered Order list.
4. Records to hand over picks from the scenario's spare records or the Lab library.
5. Answer differently when… gives a round a different answer when the trainee has done something (or has not). Pick the facts from the list, worded as sentences; a field you leave blank keeps the round's answer.
6. Write the words in each of your organization's languages (Words in). A language you have not written uses your default language's words. Words are plain text — no formatting.

Saving a Script

Save checks the script with the same rules as Realizer's packs — fictional names and addresses only (reserved e-mail domains such as example.org, no real phone numbers or identifiers), records that exist, and facts the register can read — and lists anything to fix at the top and on the round it concerns.

A saved script answers from the next time the person is asked, in every case of that scenario in your organization, and it replaces the scenario's whole script for that person. Clear Use our script to switch it off (the scenario's script answers again); Remove our script deletes it.

Adding a Person

Add a person adds a member of your staff the scenario does not have — a name, a job title, a unit, initials, a fictional e-mail and the parts they play — with their script. They appear in Lab mode tagged Simulated, and the trainee can hand them work as to a colleague. You cannot add someone outside your organization: the requestor, third parties, the complainant and the regulator's contact belong to the case.

Trying It

Try it in Lab mode (on a practice scenario) opens Lab mode at the scenario so you can start a practice case and watch your script answer. For a team simulation, a lead planning it can also choose Write 's script for this simulation: that script answers in that simulation only, over your organization's and the scenario's, and is checked when the plan is saved. See Team Exercises.

What Is Recorded

The audit ledger records each module created, deleted, sent for approval, approved, published (with whether it was a material change) and retired, each change to your blocks on pack modules, each audience rule created, changed or deleted, and each change to Open to Browse — facts only, never the text you wrote. Changes to glossary terms and obligations are kept in the audit history like other configuration.

Related Pages

• Our Practice on Pack Modules — adding your practice to a jurisdiction pack's module.
• Learning Paths — putting modules on a learning path and its settings.
• Audience Rules — enrolling the right people automatically.
• My Learning — what learners see.
• Coach Notes — the Studio's Coach tab.
• Training Cases — the practice cases behind Exercise steps.
• Settings → Training — publish review and who sees check results.