Quire
/admin/extensions lists what is built into your installation and which of it
your organisation uses. Quire treats everything it ships at an extension point
the same way: activity types, blocks on the home page, enrolment methods,
sign-in methods, question types, reports, themes and integrations such as xAPI
and HubSpot are each an extension with a name, a version and a status.
Switching one on or off
The page groups extensions by the kind of thing they add, and each group says how many are on for your organisation. Switch off stops an extension everywhere in your organisation at once, and Switch on restores it. What it already recorded stays:
- Activities, questions, enrolments and files already made keep working.
- A file already exported stays downloadable.
- What is refused is new use: saving a new activity of that type, adding that enrolment method to a course, creating a question of that type, opening or exporting a switched-off report, using a switched-off sign-in method, or changing an integration.
Foundations cannot be switched off and show Always on: password sign-in, the manual, self and API enrolment methods, the description question type, the audit reports and Quire’s own theme.
Extensions that affect where people sign in are worth a second look before you switch them off. Turning off a sign-in method that some of your people rely on stops them signing in by it.
Adding your own
An extension is code. Extensions are compiled into Quire when it is built, by whoever runs the installation, and there is no way to load one at run time or from a tenant. On a hosted plan that means the list you see is the list Quire provides. On a self-hosted installation, your team writes an extension against the contract for its point, registers it where the web application and the worker are composed, and rebuilds the image; the developer guide has the outline. Extension code runs inside Quire’s trust boundary, and a dependency it brings must pass the same licence check as Quire’s own.