Training & credentials

Training in MakerOps runs one chain end to end: a member takes the training, the credential lands on their record, and the machines that require it start working for them — nothing re-entered, no paper card catalog.

Courses and content

Training content is authored in the platform’s slide editor — slides with text, images, annotated callouts, and interactive elements — and renders on both web and the mobile app. Existing material has a place too: presentations can be imported and video can be part of a course, and SCORM-packaged courses from an existing LMS can be brought in.

Structure a course as slides plus checks; completion is tracked per person.

Credentials and skills

Two kinds of records come out of training:

• Credentials — the formal clearances (“Laser Cutter Certified”) that gate machine access and can expire or be revoked.
• Skills — lighter-weight abilities staff can mark on a person, useful for badging and finding help on the floor.

Both can be issued automatically on course completion or granted manually by staff (for the member who tested out in person). Prerequisites compose: a credential can require prior credentials with AND/OR logic, so “Advanced CNC” can require “CNC Basics” plus either shop orientation path.

Gating the machines

Each piece of equipment lists the credentials required to run it. With MakerOps machine controllers installed, the check is enforced at the machine itself — the scan at the controller verifies credentials and waivers in real time (see Machine access). Without controllers, the same records back staff checks and reporting.

Running it at scale

Academic spaces onboarding hundreds of students at term start typically: enable self-registration or SSO, put the orientation course first with everything else prerequisite-locked behind it, and let the queue work itself — staff watch completion dashboards instead of running orientation lectures.