Configure

Where Accreditation's account-wide settings are stored, why an out-of-date copy is refused when you save, and what the Portal can and cannot do with these settings.

The three ready-made Accreditation roles you can assign to staff — read only, day-to-day user, and administrator — what each one opens, and why only the administrator role reaches Setup and Billing.

How to create and maintain the accreditation programs your organization runs, order them for display, and understand what happens when you delete or deactivate one.

Define the stages a school moves through in a program, put them in the right order, decide whether an advancement run keeps a school in its phase or moves it to a named next phase, and set how expiration dates are recalculated on entry.

Add a report type to a phase, decide who at the school may view or submit it, use a different form than the report type's own, and understand why changing a requirement doesn't immediately update what schools already in the phase owe.

How to create, edit, and retire the reusable email templates staff send to a site visit's team, choose whether the whole team or only certain roles receive one, and record which programs it's meant for.

Set up who on a visiting team may evaluate whom, choose or design the forms team members fill in, write and preview a confirmation email, and retire or delete a process without disturbing visits that already use it.

What an evaluation type stores, how it differs from an evaluation process, and why creating or changing one currently has no effect on evaluations, processes, or what team members see.

Create and edit the reusable email notices you send to school contacts, limit a notice to certain contact roles, insert school and program details, and retire or delete a notice you no longer use.

Define a reusable billing template with date ranges relative to when it's used, understand what happens to a template's jobs when you switch one off, and retire or delete a template you no longer want offered.

How an application process for a program is put together through the API today, the forms and emails it can require, and why previewing its email currently fails.

How to send a real copy of an accreditation notice's or team notice's current email to any address you choose, filled in with a real school or visit, before you rely on it.

How to schedule a billing template to create a billing run automatically on a repeating basis, and what stops a schedule from being deleted once it has produced a run.

How to set up the reasons staff can give for a report's status, retire a reason without losing it from reports that already use it, and why a reason still in use can't be deleted.

How to define the kinds of report your schools and teams submit, choose the form and Portal display each uses, and why a report type or the form it relies on can't be deleted while something depends on it.

How to set up the confirmation email that follows a report submission, preview exactly what a submitter will receive, and why a process still in use can't be deleted.