What the product does
User, participant and content allowances are defined by the selected Guardian package.
Guardian University combines published learning, assignments, progress, assessments, certificates, recommendations and human-risk remediation with the same action model used elsewhere in Guardian.
Guardian for Australian customers is built, operated and hosted in Australia. All Guardian customer and platform data, including backups and recovery copies, is maintained and stored within Australia.
Guardian retains assignment, progress, assessment attempts, completion, certificate, content version and approved recommendation history. Customer access remains role and tenant scoped.
The package schedule identifies staff users, participants, included courses, content rights, custom-content allowance, support, reporting and any provider-sponsored participant capability.
Risk factors and recommendations must be based on approved learning, policy or security context and remain explainable to authorised reviewers.
User, participant and content allowances are defined by the selected Guardian package.
The same records support learner progress, customer oversight and authorised provider operations.
Bespoke course creation and campaign work remain separate where outside the included allowance.
Annual awareness training often records attendance without connecting content to role, policy, overdue behaviour, incidents or the remediation required after a human-risk event.
Guardian University provides a structured learner experience and an operating view for businesses and providers. Learning, assessment and recommendations can create accountable follow-up without turning an automated score into an unexplained judgement about a person.
Select published courses, pathways and policy content according to role, risk, onboarding or remediation need.
Track assigned, in-progress, completed, failed and overdue learning without manual spreadsheets.
Create recommendations and actions when a policy gap, event or human-risk factor requires follow-up.
User, participant and content allowances are defined by the selected Guardian package.
Give learners one place to see assigned, in-progress, recommended and completed content.
Organise published content by role, audience, pathway, category, difficulty and prerequisite.
Assign courses or policies to approved users or groups with due dates and status.
Record attempts, scores and completion according to the published course version and rules.
Issue certificates where the eligible course and assessment conditions are satisfied.
Present explainable factors, recommended learning and required follow-up within the customer scope.
The same records support learner progress, customer oversight and authorised provider operations.
Assigned work, due dates, progress, completion, certificates and recommended learning.
Completion, overdue assignments, group performance, recommendations and remediation actions.
Authorised customer learning, assignments, completion and overdue work within provider relationships.
Approved cyber-safety learning, checklists, notices and completion without continuous paid monitoring or agents.
Explainable factors, evidence, recommendations and relevant learning without opaque autonomous conclusions.
Assigned, completed, overdue, assessed and certified state based on published course versions.
Bespoke course creation and campaign work remain separate where outside the included allowance.
Publish approved courses, modules, lessons, policies, quizzes and certificate rules.
Configure roles, groups, onboarding, due dates, prerequisites and required learning.
Review completion, overdue work, failed assessments and customer or provider follow-up.
Connect approved human-risk events or gaps to suitable published learning and actions.
Manage publication, version, supersession and retirement so completion remains tied to the correct content.
Provide learning, assessment, overdue, certificate and human-risk reports according to scope.
Published content and controlled completion rules protect the integrity of progress and certificates.
Approve and publish the course, policy or pathway version and its completion rules.
Assign content to approved users or groups with the correct due date and customer scope.
The learner completes modules, lessons, video, reading, acknowledgement and activities.
Quiz or assessment rules determine whether the course requirement is met.
Guardian records versioned progress, completion, certificate and supporting status.
Overdue, failed or risk-linked learning drives follow-up, reassignment or customer action.
The product supports staff, provider and approved participant experiences with different entitlements.
Assign baseline cyber, privacy, policy and role-specific learning to new staff.
Run required recurring content with due dates, assessment and completion evidence.
Assign targeted learning after a phishing event, policy breach or human-risk finding.
Operate staff programs and provide approved Participant Free cyber-safety content.
Manage authorised customer assignments, completion and reporting through provider scope.
Publish required policy content and retain versioned acknowledgement and completion.
These details remain explicit before activation, but are grouped into one operating view so buyers can review the responsibilities without working through four separate page sections.
Onboarding defines audiences, content, completion rules and follow-up responsibilities. The customer provides user and group information, role structure, onboarding needs, required policies, recurring content, due-date rules, certificate expectations, reporting audience and the provider relationship where relevant. Damocles maps published content to pathways and assignments, validates learner access and tests progress, assessment, completion and certificate behaviour before launch. Go-live includes communication, support, overdue follow-up, version management, reporting and the boundary to bespoke content production, simulated campaigns and specialist human-risk work.
University can connect approved identity, HR or security context without making one external system mandatory. Supported connectors may provide approved users, groups, roles, assignment triggers or security events. Guardian remains responsible for customer scope, published content, assignment, progress and remediation state. A new connector is reviewed for identity authority, customer mapping, field quality, privacy, synchronisation, deletion, role changes and supportability before it is represented as available. Security events or risk factors can recommend learning, but automated signals do not make disciplinary or employment decisions and do not replace human review.
Learning records remain tied to the published course version and controlled completion rules. Guardian retains assignment, progress, assessment attempts, completion, certificate, content version and approved recommendation history. Customer access remains role and tenant scoped. Completion is not inferred from opening a page. The published course determines the modules, lessons, acknowledgements and assessment conditions required. Reports distinguish assigned, overdue, in-progress, completed and failed states and avoid presenting unsupported participation or risk conclusions.
Guardian Core includes University and Human Risk within the approved user and content allowance. The package schedule identifies staff users, participants, included courses, content rights, custom-content allowance, support, reporting and any provider-sponsored participant capability. Participant Free includes approved low-cost cyber-safety content and does not include continuous personal dark web, endpoint, DNS, SMS or analyst monitoring. Bespoke course development, custom video, large-scale campaign work, additional users and content outside the allowance may be separately priced.
The exact answer is confirmed in the proposal and package schedule, but these points should be understood before activation.
Approved customer content can be published where rights, format, workflow and package allowance support it.
Yes using supported customer groups, roles and provider scope.
Only where the published course is eligible and the defined completion and assessment rules are satisfied.
Participant Free provides approved cyber-safety learning and checklists without paid continuous monitoring or agents.
Yes where an approved workflow maps the event or human-risk recommendation to published content and human review.
Human-risk factors remain explainable and support review. The product does not make opaque disciplinary or employment conclusions.
Risk factors and recommendations must be based on approved learning, policy or security context and remain explainable to authorised reviewers.
The product does not imply autonomous disciplinary decisions, unrestricted phishing delivery or complete measurement of human behaviour.
User counts, content rights, assignment rules, campaign work and specialist content remain within the selected package and approved scope.
We will map audiences, content, pathways, due dates, assessment, participant capability, reporting and human-risk follow-up.