Account, Billing & Settings
TeachFORGE.ai
Account, Billing & Settings / Organisation admin
The organisation admin portal
A map of what an administrator controls, so you know what to ask for.
Not a teacher page. Worth knowing exists.
Who can open it
Only members with the organisation administrator role, and only with two-factor authentication enabled. An ordinary teaching account never sees it.
It is described here because most of the things a teacher cannot change are changed from it, and knowing the page name makes the request specific.
The five pages
| Page | What is managed |
|---|---|
| Overview | The organisation's name, data region and seats used against the limit; the security policy; allowed email addresses; the licence seat list with the ability to release one; and Organisation details, the country, postal address and tax number used on the organisation's invoices. |
| Members | Each member's email, match and entitlement, with unlink and erase actions, the organisation data export, and the deletion request. |
| Hosting | The organisation's own sign-in addresses, the DNS records to add, and a check. |
| LMS | The LTI 1.3 connection: the tool details to copy into the learning platform, and the platform details to enter here. |
| Storage | The organisation's own object storage, with usage broken down by product and by volume. |
Adding people
People join through the Allowed emails list on Overview. Only people on the list can join, and each person joins when they accept.
An email domain comes first. Until TeachForge staff have recorded your organisation's email domain, the list is switched off under the heading An email domain must be recorded first, and your people use TeachForge with their own individual accounts. Ask TeachForge support to record the domain. Once it is recorded the page reads You can add addresses ending in: followed by your domains.
You can add only addresses on those domains. Any other address is refused, line by line, with the message that it is outside this organisation's email domains and that TeachForge staff can add it for you.
The list has a Status column: Waiting for the person to join or Joined. Waiting reads the same whether or not the address already has a TeachForge account. Removing an address does not remove someone TeachForge staff assigned by hand.
Someone who already has an account is not moved when you add them. They are sent an email and see an invitation when they are signed in, and they join only if they accept. See When an organisation covers your account for what they are shown.
The portal also shows one line about the Terms of Service: who accepted them for the organisation and when, or that acceptance is not yet recorded. Record acceptance is for an administrator who has the organisation's authority to accept. It is recorded once, with their name and the date.
What to ask for
The requests a teacher most often needs, and where each lands.
- Our student IDs look like this and the pattern is not in the list — the pattern is set by TeachForge support at the organisation level, and the LMS page blocks setup until one exists.
- I need Quest Ladder / the Virtual Lab — a seat at the right tier, from Overview.
- We want learners to launch from our learning platform — the LMS page, done once.
- We need our own sign-in address — Hosting, plus DNS records at your provider.
- Our data must sit in our own storage — the Storage page.
- We need to add colleagues — the Allowed emails list on Overview, once TeachForge support has recorded your email domain.
- Our invoices need our address or tax number — Organisation details on Overview. If you cannot fill them in yourself, TeachForge support can fill them in for you.
Three of these are not self-service even for an administrator. The default student ID pattern, adding a subdomain and recording an email domain all go through TeachForge support, and the pages say so rather than offering a control that would not work.
Leaving, and deleting
An administrator can unlink a member without deleting their account, or erase their data — both asking for an authenticator code first.
Deleting the organisation is deliberately slow. The export must be ready first — deletion cannot be requested until the archive is — a choice of unlink or erase is made for each member, and a platform administrator has to approve the request.