Skip to main content

Tenant Admin

Run a tenant: its settings, members, alerts, standards, starter files and maintenance.

For tenant admins · Open this screen

Tenant Admin is for a tenant’s tenant admins (and site admins). Open it from the home page’s Quick Links. Choose the tenant at the top; each tab loads when you first open it, and the address remembers the tab (#users), so you can bookmark one.

General

The tenant’s own settings. Edit tenant to change them:

  • Name and description.
  • Read access: whether only members may read the tenant, or every signed-in account may read it and sit its tests. Reading never lets anyone edit.
  • Stimulus placement: where an item shows a stimulus it uses but does not place itself: Beside the question, Above the question or Below the question.
  • Export metadata: what the export dialog offers first, metadata inline in the manifest, as files of their own, or none.
  • Invalid exports: whether a package the validator finds errors in can still be downloaded, or is refused with only its findings kept.
  • Features: what a site admin has turned on for the tenant, such as elevated roles and whole-bank export.

Users

The tenant’s members and their roles. Tenant admins manage this page; authors create and edit; reviewers read; test takers sit tests.

  • Add a member by username. The account must exist already.
  • Create user makes a new account that belongs to this tenant only. When the site can send email, the person gets a link to choose a password; otherwise AIB shows you a temporary password once, to pass on.
  • Change a member’s roles, or remove them.

A tenant always keeps at least one tenant admin. Giving someone the author or tenant admin role needs the tenant’s elevated roles feature, which a site admin turns on; reviewer and test taker can always be given.

Alerts

Banners on the home page for this tenant’s members. Add alert with a message, a style (information, warning, danger…), who it is shown to (everyone, creators, or test takers) and an optional expiry. Delete an alert to stop it showing at once; a site admin can restore it.

Test Sessions

Every attempt at this tenant’s tests, with who sat it and its state. Abandon ends one in progress without scoring it; it is kept, marked abandoned, and cannot be resumed.

A draft someone left open is not listed here. Open its resource and choose Override draft to take it over, then discard it.

Metadata Profile

The profile decides the Metadata tab’s form on every item, test and section: which fields, their labels, and the lists their values come from. Download the default profile, change it, and upload it. You can also upload standards lists (curriculum frameworks) for the standards picker.

A profile or list that fails its schema is not stored, and you are told why. Changing the profile changes no existing record; fields it no longer names are kept, under “Other fields”.

To add Subject and Grade fields, give each a list of its values and make it a classification field. The profile’s comments show how. Each is stored as a LOM classification (subject as a discipline, grade as an educational level), so other systems that read LOM understand it, and both can be shown, sorted and searched on the Resources page.

Classes

The class field in the editors offers the QTI shared vocabulary of style classes that fits the element being edited. Here you decide which classes the tenant prefers, which go on new questions by default, which are hidden, and you add classes your own stylesheets define. You can also stop authors typing classes that are not listed.

The editor also ranks what the bank already uses and each author’s recent picks. Rebuild refreshes the bank’s summary after a large change.

Data attributes

QTI lets content carry attributes of your own, named data- anything. This tab is the tenant’s dictionary of them: each name, where it may go, what kind of value it takes, and sets of values the editor offers. A set can depend on the element, on another attribute’s value (on the element or around it), and on where the element sits, so data-topic can offer different topics depending on data-subject.

Below the dictionary, the names the bank already carries are listed; Add to dictionary makes a card from one for you to review. Nothing is ever removed from content for not fitting; it is only marked.

Starter Files

The templates the Create menu copies from, one per interaction type plus a blank of each kind. They are the tenant’s own: rename them, edit them into your house style, give them a description, or add new ones (a new starter is a copy of an existing one). Changing a starter changes everything created from it afterwards, never what was created before.

Sample Content

Worked examples shipped with AIB: an item for each supported interaction, a stimulus, sections, tests and their media. Deploy them into this tenant to explore or to copy from. They are ordinary resources, listed on Resources. Deploying again updates a sample only if AIB’s copy has changed, and leaves alone one you have edited.

An item a sample test uses is locked while that test is locked, as for any test.

Utilities

  • Export the whole bank as one QTI 3.0.1 package: the newest version of everything, or every version. Anything that cannot be exported is left out and listed. The package is on Exports. It needs the tenant’s whole-bank export feature, which a site admin turns on under General; a site admin can always export.
  • Verify Manifest checks the bank’s manifest against what it holds, both ways, and changes nothing.