PPaT Wiki
DocumentationPathwayBase de connaissancesForumBlogContact
Week streakFOUNDATION0 badge
Langue: Français
  • English
  • Nederlands
  • Karen (S'gaw)
  • Français
  • Deutsch
  • Lea faka-Tonga
  • Te reo Māori
Poser une question à la communauté

Your PaT Pathway

0/46
Foundation
0/43
Practitioner
0/37
Advanced
0/20
Super User

Practitioner

  • ○Pop-Out Chat Feature (not passed yet)
  • ○Chat reminder (not passed yet)
  • ○Chat to SD (not passed yet)
  • ○Chat to email to chat (not passed yet)
  • ○Email to chat to email – non PaT users (not passed yet)
  • ○C2E Attachments (not passed yet)
  • ○Email to BFF (not passed yet)
  • ○How SD chats work with SD Members and External Users (not passed yet)
  • ○Docked Chats (not passed yet)
  • ○Inline chats (not passed yet)
  • ○Multi-Tasks (not passed yet)
  • ○Task Integrity: what it is and why it drops (not passed yet)
  • ○Chat to task to project (not passed yet)
  • ○SD Task wall view (not passed yet)
  • ○Using SDs as a report or meeting minutes app (not passed yet)
  • ○Running Meetings with SDs (not passed yet)
  • ○Invite Attendees (not passed yet)
  • ○Recurring tasks: create and edit (not passed yet)
  • ○Info Icons (not passed yet)
  • ○Moving Section Headers (not passed yet)
  • ○SD Element Categorisation (not passed yet)
  • ○Add any Image as a Section Header Icon (not passed yet)
  • ○Embedding SDs in SDs (not passed yet)
  • ○Assigning an SD to a new parent (not passed yet)
  • ○Filing and retrieving SDs (not passed yet)
  • ○SD Owner Functions (not passed yet)
  • ○Docking SDs and Updating Images (not passed yet)
  • ○Embedding live data in an SD (graphs and spreadsheets) (not passed yet)
  • ○PaT AI (not passed yet)
  • ○Track Engagement (not passed yet)
  • ○Share and record your screen (not passed yet)
  • ○Different Form Uses (not passed yet)
  • ○Form Wall (not passed yet)
  • ○SD Form Responses: finding and exporting form responses (not passed yet)
  • ○Video rooms: guests joining and asking to record (not passed yet)
  • ○Comprehension Audits (not passed yet)
  • ○Evidential audits: completing one (not passed yet)
  • ○LMS Architecture (not passed yet)
  • ○Safe Walks (not passed yet)
  • ●Customer-specific training: how it works (this page)
  • ○How PaT Manages Inactive Users (not passed yet)
  • ○How to unlock a module for a staff member (not passed yet)
  • ○Health and safety templates (not passed yet)
  • Company Structure: adding a new user
  • Company Structure: customer companies
  • Company Structure: departments, job titles and roles
  • Company Structure: modules for a site or a country
  • Company Structure: process categories
  • Connections: linking PaT to Microsoft 365
  • Forms - API Integration
  • How to create a campaign for the PaT Lite training portal
  • How to edit an existing Bulletin Board Post
  • How to set up your SD Map
  • LMS Feedback: learner ratings and comments
  • LMS Metrics - If you can't measure it, you can't manage it
  • Manage users
  • Pacing recertifications and escalations
  • PaT Business Unit Template Overview
  • SD Workflows - Multi Submit
  • SD Workflows - Workflow Settings
  • System Activity: escalations, logins, emails and more
  • System Config: company settings
  • The org chart
  • Add any Image as a Section Header Icon
  • Assigning an SD to a new parent
  • C2E Attachments
  • Chat reminder
  • Chat to email to chat
  • Chat to SD
  • Chat to task to project
  • Comprehension Audits
  • Customer-specific training: how it works
  • Different Form Uses
  • Docked Chats
  • Docking SDs and Updating Images
  • Email to BFF
  • Email to chat to email – non PaT users
  • Embedding live data in an SD (graphs and spreadsheets)
  • Embedding SDs in SDs
  • Evidential audits: completing one
  • Filing and retrieving SDs
  • Form Wall
  • Health and safety templates
  • How PaT Manages Inactive Users
  • How SD chats work with SD Members and External Users
  • How to unlock a module for a staff member
  • Info Icons
  • Inline chats
  • Intégrité dans l’exécution des tâches : ce que c’est et pourquoi elle diminue
  • Invite Attendees
  • LMS Architecture
  • Moving Section Headers
  • PaT AI
  • Pop-Out Chat Feature
  • Recurring tasks: create and edit
  • Running Meetings with SDs
  • Safe Walks
  • SD Element Categorisation
  • SD Form Responses: finding and exporting form responses
  • SD Owner Functions
  • SD Task wall view
  • Share and record your screen
  • Tâches multiples
  • Track Engagement
  • Using SDs as a report or meeting minutes app
  • Video rooms: guests joining and asking to record
  • Activity Notifications
  • Add members and set permissions
  • AI Summary: a quick summary of an SD
  • Capture and Manage Accidents
  • Capture and Manage Hazards
  • Chat to task
  • Chat Wall
  • Contextual Communication
  • Convert a Note to a Task
  • Create a new SD
  • Créer une tâche
  • Critical Chrome Extensions
  • Document Store: shared links, your folders and favourites
  • Fast Notes
  • Gestion des tâches
  • Getting help: the PaT Helpdesk
  • Global Search
  • Group Chats
  • How to embed Outlook onto your PaT
  • How to resize your browser to best view PaT
  • How to use the PaT Lite training portal
  • Insert links
  • Module Learning - Desktop
  • Module Learning - Mobile
  • Mur des tâches
  • My Profile
  • Newbie PaT Intro – Chats and SDs
  • Notes
  • Out Of Office: turning it on, and the calendar on your Task Wall
  • Outlook 2FA Issue
  • PaT Mobile App – Overview
  • Présentation du chat PaT
  • Preview, download and share files
  • Publish a Bulletin Board Post
  • Reading an SD in another language
  • SD Elements
  • SD Main page useful features
  • SD Overview
  • Section Headers
  • Security measures for multiple users on a device
  • Share Feedback
  • Signing in to PaT and resetting your password
  • Système de gestion des tâches
  • Traffic light progress
  • Upload file attachments
  • Video calls on the mobile app
  • Build a reporting system
  • Chat Management - Pro Tips
  • Comment les responsables peuvent activer l’absence du bureau (OOF) pour les membres de leur équipe
  • Conditional Formatting
  • Configuring a UDF: columns and calculated columns
  • Configuring a UDF: filters, grouping and endpoint details
  • Customer-specific training: setting it up
  • Endpoint Manager: finding endpoints and building your own UDF
  • Escalade automatique
  • Form builder: field types
  • Forms - Extract Data (the AI form builder)
  • How to build modules in the Module publisher
  • How to create module comprehension audits
  • How to create module evidential audits
  • How to create module quizzes
  • How to embed an SD into the LMS
  • How to make form templates live for everyone to use
  • How to upload form elements to an SD
  • How to use the PAR SD
  • Live H&S Reporting
  • Mastering the Business Strategy Template
  • Mode test du formulaire
  • Module Admin: finding and managing modules
  • Module Completion Notification Setup
  • Module Publisher Content Options
  • PaT SD Map Overview
  • PaT SD Map Presentation
  • PaT SD Templates Overview
  • Pure Forms
  • SD Dashboard: building a dashboard
  • SD Forms
  • SD Security Settings
  • SD Template Helper Functions
  • Strategy System
  • Throttling
  • Using Chat to SD to go from being a good manager to a great one
  • Using SDs as the LMS Document
  • PaT Lite : les principaux aspects de PaT que vous devez comprendre
  • Qu’est-ce que PaT et pourquoi est-ce important ?
  • PaT Lite : de la discussion à la tâche
  • PaT Lite : présentation des Strategy Documents
  • PaT Lite : philosophie fondamentale — normes et exécution tactique
  • PaT Lite : des outils intelligents qui réfléchissent avec vous
  • PaT Lite : L’avenir des entreprises, c’est la culture
  • Bienvenue sur le wiki PaT
  • Configurer votre espace de travail
  • Votre première semaine
  • Strategy Documents
  • Tâches et affectations
  • Modèle d’autorisations
  • Chat et discussions
  • Formulaires et soumissions
  • Tableaux de bord et rapports
  • Gestion des utilisateurs
  • Paramètres de l’espace de travail
  • Connexion à un système comptable
  • Authentification unique
  • Présentation de l’API
  • Jetons d’accès
  • Webhooks
0/46
Foundation
0/43
Practitioner
0/37
Advanced
0/20
Super User
Practitioner quizzes: 0 of 43 passed
  • ○Pop-Out Chat Feature (not passed yet)
  • ○Chat reminder (not passed yet)
  • ○Chat to SD (not passed yet)
  • ○Chat to email to chat (not passed yet)
  • ○Email to chat to email – non PaT users (not passed yet)
  • ○C2E Attachments (not passed yet)
  • ○Email to BFF (not passed yet)
  • ○How SD chats work with SD Members and External Users (not passed yet)
  • ○Docked Chats (not passed yet)
  • ○Inline chats (not passed yet)
  • ○Multi-Tasks (not passed yet)
  • ○Task Integrity: what it is and why it drops (not passed yet)
  • ○Chat to task to project (not passed yet)
  • ○SD Task wall view (not passed yet)
  • ○Using SDs as a report or meeting minutes app (not passed yet)
  • ○Running Meetings with SDs (not passed yet)
  • ○Invite Attendees (not passed yet)
  • ○Recurring tasks: create and edit (not passed yet)
  • ○Info Icons (not passed yet)
  • ○Moving Section Headers (not passed yet)
  • ○SD Element Categorisation (not passed yet)
  • ○Add any Image as a Section Header Icon (not passed yet)
  • ○Embedding SDs in SDs (not passed yet)
  • ○Assigning an SD to a new parent (not passed yet)
  • ○Filing and retrieving SDs (not passed yet)
  • ○SD Owner Functions (not passed yet)
  • ○Docking SDs and Updating Images (not passed yet)
  • ○Embedding live data in an SD (graphs and spreadsheets) (not passed yet)
  • ○PaT AI (not passed yet)
  • ○Track Engagement (not passed yet)
  • ○Share and record your screen (not passed yet)
  • ○Different Form Uses (not passed yet)
  • ○Form Wall (not passed yet)
  • ○SD Form Responses: finding and exporting form responses (not passed yet)
  • ○Video rooms: guests joining and asking to record (not passed yet)
  • ○Comprehension Audits (not passed yet)
  • ○Evidential audits: completing one (not passed yet)
  • ○LMS Architecture (not passed yet)
  • ○Safe Walks (not passed yet)
  • ●Customer-specific training: how it works (this page)
  • ○How PaT Manages Inactive Users (not passed yet)
  • ○How to unlock a module for a staff member (not passed yet)
  • ○Health and safety templates (not passed yet)
  1. Documentation
  2. Practitioner
  3. Customer-specific training: how it works

Cette page n’a pas encore été traduite et s’affiche donc en anglais.

Customer-specific training: how it works

Summary PaT decides which training each person gets through a three-tier structure, the LMS module-to-role-to-job-title architecture. Every employee has a job title, each job title is made up of…

Sur cette page
  • Steps
  • Step 1
  • Step 2
  • Step 3
  • An example
  • Step 4
  • Step 5
  • Step 6
  • Step 7
  • Step 8
  • Adding customer-specific training
  • Step 9

Summary PaT decides which training each person gets through a three-tier structure, the LMS module-to-role-to-job-title architecture. Every employee has a job title, each job title is made up of roles, and each role is linked to a set of training modules. When a person is given a job title, they automatically receive every module linked to its roles. The example below is a warehouse job title made up of three roles. Customer-specific training is then added on top of this structure.

Steps

Note. This is part 1 of customer-specific training. It explains how training modules are assigned to roles, how a collection of roles makes up a job title, and how a person who is given a job title inherits, through this structure, the modules they need to do their job. Customer-specific training builds on this structure.

Step 1

In PaT, every employee has a job title.

Step 2

Under each job title there are specific roles, which define what an employee is responsible for. A job title is a collection of roles.

Step 3

Each role is then linked to a set of training modules. This three-tier structure is called the LMS module-to-role-to-job-title architecture. It is how PaT makes sure that employees receive the training they need for their job functions.

An example

Step 4

For example, take a team member in a warehouse's Inwards department whose job title is Ops Level 1 - Inwards team member. That job title is made up of the three roles in Steps 5 to 7.

Step 5

The first role is Ops Level 1 - Inwards team member, with the same name as the job title: every job title always has a role of the same name. This role includes all the training needed to carry out the duties expected of a junior inwards staff member, such as devanning container procedures and basic reporting.

Step 6

The second role is Storesperson. It includes the training that all operations staff need at all levels, such as time sheets, keeping a tidy work area and the inventory system.

Step 7

The third role is All Staff. It includes the training that all staff in the organisation need, such as H&S (health and safety) and company policies.

Step 8

Because of this structure, when the team member is given the job title Ops Level 1 - Inwards team member, they are automatically assigned all the training modules linked to the roles in that job title. In the same way, everyone who is given a job title inherits the modules they need to do their job.

Adding customer-specific training

Step 9

Customer-specific training is added on top of this structure, to make sure people are also trained on any customer-specific responsibilities they need to carry out as part of their job. The Customer-specific training: setting it up module covers how it works.

Check yourself

Checking your PaT sign-in…

PrécédentComprehension AuditsSuivant Different Form Uses

Sur cette page

  • Steps
  • Step 1
  • Step 2
  • Step 3
  • An example
  • Step 4
  • Step 5
  • Step 6
  • Step 7
  • Step 8
  • Adding customer-specific training
  • Step 9
PPaT Wiki

Documentation, base de connaissances et assistance communautaire pour People and Tasks.

Documentation

  • Premiers pas
  • Concepts fondamentaux
  • Intégrations
  • Référence de l’API

Assistance

  • Base de connaissances
  • Forum communautaire
  • Nous contacter
  • État du service

Entreprise

  • PaT
  • Blogue
  • Conditions d’utilisation
  • Confidentialité

© People and Tasks. Tous droits réservés.