Admin / Editor · Allow about 12 minutes
Before you begin
An Owner or Admin must approve the compliance policy. Use a published journey revision with the required learning activities and a deliberate initial rollout. Authoring roles may use certificate actions within their permitted knowledgebase scope. Recurrence requires Beetl’s scheduled worker to be running.
1. Prepare the revision and approve a policy
Open Learning Studio → Learning library → Assessment tools → Journey placement. Check the exact Published revision. Attach needed activities to a draft revision first and follow the separate journey approval/publication workflow before choosing the published revision here.
An Owner or Admin enters the Human-approved assignment basis: explain why the identified audience receives this learning. Beetl does not infer a legal obligation or decide who must comply.
Choose Recurrence: None, Monthly, Quarterly, Biannual or Annual. Set a valid Timezone and Due after days; a recurring policy needs a due period. Review Escalate after days without assuming it alone proves a reminder has been delivered.
Enable only requirements that exist as required activities on that revision: passed assessment, acknowledgement or practical approval. For certificates, enable Issue internal completion certificates and enter a plain-language Certificate title, Issuer name and optional Expiry days.
Read the complete policy and choose Approve policy only when the audience basis and requirements are authorised. Editors can author learning, but cannot approve this policy through either the screen or a direct request.
2. Verify the initial rollout and recurring work
Create the intended initial rollout through Delivery and check its recipients and pinned revision. A policy without an initial source assignment does not create an audience by itself.
Recurrence uses the chosen calendar period and timezone. It is not an anniversary counted from each learner’s completion. The worker considers existing source-rollout recipients who are still workspace members, excluding people with an active assignment for the same journey revision.
After the worker runs, check Delivery and the learner’s My work for the new assignment and due date. Running it again in the same period must not create a duplicate occurrence. Do not repeatedly launch a manual rollout while waiting for scheduled processing.
If scheduled work does not appear, have an Admin or support check worker health, policy revision, source assignment, calendar period and active enrolments. A configured schedule is not proof that the worker has run successfully.
3. Issue, verify and maintain internal certificates
Open Assessment tools → Records and inspect Compliance completion status. The learner must have completed the assignment and satisfied every configured evidence requirement before Issue if eligible can succeed.
Choose Issue if eligible for the intended completed enrolment. Review Certificate history and open the verification link. Issuing again for the same active certificate returns that existing record rather than creating duplicates.
Treat the verification link as shareable information: its public view includes the learner display name, journey, issuer, dates and current validity. Share it only with the appropriate audience; do not place learner links in public Help screenshots.
Use Revoke with a meaningful reason for an invalid certificate, or Reissue with a reason when a corrected replacement is appropriate and evidence is still eligible. Check the new verification result and the retained predecessor history.
These are internal completion records. They do not provide external accreditation, professional certification, or a legal compliance determination.
Check your result
The approved policy matches an explicit audience and published revision, recurring assignments are checked for the correct period, and certificate validity can be traced through retained history.
If something goes wrong
Approval denied: use an Owner or Admin and verify the published revision. Editor authoring permission does not grant compliance-policy approval.
Requirement rejected: add the matching required activity to the journey, complete its approval/publication workflow and choose the correct published revision.
No new recurring assignment: confirm a source rollout exists, the worker ran, recipients still belong to the workspace, and an active enrolment or an already-processed period is not suppressing another assignment.
Certificate ineligible: check assignment completion and the configured assessment, acknowledgement and practical evidence. An exemption is not completion.
Verification says invalid: check expiry, revocation and replacement history before reissuing. Never describe an internal record as professional accreditation.