Learn · Certification · Knowtation for developers

Technical: roles and proposals

A viewer reads, an editor creates a proposal, and an authorized approver decides whether it is applied to the vault.

An evaluator records an evaluation and can approve only when that permission is enabled for that person.

One Hub instance serves one vault, so separate schools can use separate Hub instances with their own roles and notes.

Invite-by-link brings a person into the Hub, while GitHub collaborator access separately governs who can clone the vault repository.

Technical: roles and proposals

Four questions. Each answer is a sentence from this lesson.

Sign up on Learn before this certificate can be emailed.

Start the course
  1. How do roles divide the class correction?

    How do roles divide the class correction?
  2. When can an evaluator approve?

    When can an evaluator approve?
  3. How should a builder separate two schools?

    How should a builder separate two schools?
  4. What access decisions must remain distinct?

    What access decisions must remain distinct?