# data[].attributes.body
All changes are requested by Licensee X via a formal channel (email).

Requests may include:

Deactivating users

Replacing users

IFRS executes:

The monitoring of completion and assessment performance (Licensee does not have insight directly)

Account deactivation

Reallocation of user seats (if capped)

# data[].attributes.custom_properties.MtzjAsCI
What level of reporting should licencees receive regarding the assessment completion of its users/learners and how often?

# data[].attributes.body
Usage and any changes monitored manually, contractually.

# data[].attributes.body
The access link that is shared with a particular licensee has a capped, token-based number of active users.

# data[].attributes.headline
Step 1: Onboarding communication, access and data request

# data[].attributes.subject
Step 1: Onboarding communication, access and data request

# data[].attributes.body
Licensee X receives an onboarding document including:

Description of the learning environment and its features.

Description of the IFRS-centralised user management approach.

The process for joining the TPP Hub learning environment

Access link to TPP Hub

Clear timelines for account activation.

# data[].attributes.custom_properties.MtzjAsCI
Strategy: Will licensees be limited to a defined number of users/learners?

# data[].attributes.body
Centralised IFRS-controlled user management (no Team Lead role)

This option does not grant the licensee team lead rights in Litmos.
All learner account creation, activation, deactivation and team assignment are managed centrally by IFRS.

# data[].attributes.body
This option gives licensees (one official licensee representative account) team lead rights in Litmos to manage their own learners (activate/deactivate accounts as staff change).

If needed, this could be paired with a capped or token-based number of active users per organisation (see question under Step 1 below). This would reduce back-end admin for IFRS, address turnover concerns within licensees, and give us ongoing visibility over the number of active licensed users.

# data[].attributes.headline
Input to Step 1: Onboarding document for Licensees about the learning enviroment, its features and functionalities

# data[].attributes.subject
Input to Step 1: Onboarding document for Licensees about the learning enviroment, its features and functionalities

# data[].attributes.body
Based on their usernames (which include the first three letters of the licensee they belong to), IFRS assigns users to their teams.

# data[].attributes.headline
The access link provided in the onboarding document in Step 1 has a capped, token-based number of active users.

# data[].attributes.subject
The access link provided in the onboarding document in Step 1 has a capped, token-based number of active users.

# data[].attributes.headline
Step 4: User management as per the Onboarding document

# data[].attributes.subject
Step 4: User management as per the Onboarding document

# data[].attributes.body
The Team X Lead (our licensee) can now add other members to its team, manage or deactivate their accounts and have insight into their assessment results.

# data[].attributes.headline
Step 3: IFRS upgrades Licensee X's account role to Team Lead 

# data[].attributes.subject
Step 3: IFRS upgrades Licensee X's account role to Team Lead 

# data[].attributes.custom_properties.MtzjAsCI
Can a user (in our case the Licensee X) be given a Team Lead role without a team (members) to manage initially? (or must there first be a team in place with users in it?) 

# data[].attributes.custom_properties.n5iVpIns
Question: Can we assign a user a Team Lead role if they are the first joiner (among their team) to Litmos and have yet to acquire team members (learners/simple users)?

# data[].attributes.headline
Step 3b: If the answer to question in Step 3 is 'no'

# data[].attributes.subject
Step 3b: If the answer to question in Step 3 is 'no'

# data[].attributes.body
The licensee uses the link provided in the onboarding document to create a simple learner account in Litmos under the licensee's legal name.

Licensee X's prospective trainers use the same link to create their accounts with the user name of their choice, followed by the first three letters of the Licensee X legal name (the first three letters will help us organise them under the Licensee X Litmos Team next)

# data[].attributes.headline
Step 3a: If the answer to question in Step 3 is 'yes'

# data[].attributes.subject
Step 3a: If the answer to question in Step 3 is 'yes'

# data[].attributes.body
The Team X leader follows the steps outlined in the onboarding document (Step 1) to enrol its team members (learners):

Sends the link to join TPP Litmos brand to prospective Licensee X trainers (Litmos learners).

# data[].attributes.custom_properties.MtzjAsCI
Can simple users be assigned to a specific team automatically (by using a specific link)? OR, can the Team Lead assign them to their team?

# data[].attributes.custom_properties.n5iVpIns
Question: Can a Team Lead assign simple users to their team themself? OR Can the invitation link to simple users be for a specific Team?

# data[].attributes.headline
Step 1: Onboarding and access to Litmos link

# data[].attributes.subject
Step 1: Onboarding and access to Litmos link

# data[].attributes.body
Licensee X receives an onboarding document that includes a link to create a Litmos account.

The onboarding document includes

text instructions on managing the team (adding learners, deactivating accounts, and monitoring assessment results).

video demo or screenshots of steps in the Litmos environment.

# data[].attributes.custom_properties.MtzjAsCI
1. Strategy: Will licensees be limited to a defined number of users per year? Do we anticipate offering the option to extend or upgrade a licence beyond that number? In other words, should we consider introducing tiered licensing levels (e.g. capped user bands such as basic, standard and premium)?

# data[].attributes.custom_properties.n5iVpIns
Questions: 
1. Can we have the Licensee X automatically assigned to TPP brand ('brand' is Litmos terminology for a specific/defined learning environment) or must we assign them to the TPP brand after they've created a Litmos account? Assuming the former but need to confirm. 
2. Strategy: Will licensees be limited to a defined number of users per year? Do we anticipate offering the option to extend or upgrade a licence beyond that number? In other words, should we consider introducing tiered licensing levels (e.g. capped user bands such as basic, standard and premium)?  

Collateral to produce: onboarding instruction document 

# data[].attributes.headline
Step 2: Licensee X representative creates a user account in Litmos

# data[].attributes.subject
Step 2: Licensee X representative creates a user account in Litmos

# data[].attributes.body
By following the link provided in the onboarding document, the Licensee X representative creates a simple user (learner) account in Litmos under the Licensee's legal name (company name).

# data[].attributes.body
Licensee X is a legal body.

The user journey of Licensee X differs from that of a simple user (learner) who is an employee of Licensee X.

Licencee X representative manages its own learners (its employees/prospective trainers).

Licensee X holds the Team Lead role in Litmos to manage team members (manage their accounts, deactivate users, and view their assessment results).

# data[].attributes.body
Links to S1/S2 e-learning, the FSA etc..

# data[].attributes.headline
If fail: try again to unlock the ppt download

# data[].attributes.subject
If fail: try again to unlock the ppt download

# data[].attributes.body
Discussion forum for users.

Enable upload file functionality for users.

Moderated?

# data[].attributes.body
A living resource, curated by the IFRS Foundation. Includes a list of commonly asked questions about the Standards' requirements and their answers.

# data[].attributes.body
This entry point can be a link in the onboarding document that is sent to licensees, for example.

Description text: Login or register to gain access to the Training Partner Programme Hub

# data[].attributes.body
Profile

Private person.

Employee of the licensee (legal body).

Can belong to a larger group of users (Litmos team) under the same licensee (legal body).

Language needs: English or otherwise

Tech needs:

onboarding (access) support

community participation support (posting and uploading files)

Communication needs:

encourage feedback about ux

encourage participation in the TPP discussion forum

# data[].attributes.body
Specs:

- Pass/fail

- Pass: 80%

- Multiple retakes

- includes conditions (if pass/if fail)

# data[].attributes.headline
TPP learning/study materials and assessment page

# data[].attributes.subject
TPP learning/study materials and assessment page

# data[].attributes.body
Includes:

script (pdf) to download for self-directed study

video recordings (mp4) of pilot training delivery

Assessment

# data[].attributes.body
Features tiles with links to: 1. TPP learning/study materials and assessment, 2. Q&A 3. TPP community and the 'news/further learning' content holder