As an admin user of your organizational account, you can:
- Manage single-sign-on options and LTI apps via the Integrations tab;
- Control your organization's license;
- Manage various organization-wide settings.
Please note that the options described here are not available on teacher accounts.
Managing SSO and LTI apps
The Organization > Integrations tab allows you to enable Google or Microsoft single-sign-on and manage LTI apps:
Azure Tenant ID: use this field to enable Microsoft single-sign-on (SSO) for your Azure Active Directory tenant. You can learn more about this integration here.
Clever District ID: If your school uses Clever for rostering, you have the option to set up a Clever integration so that whenever someone in your district registers, they will automatically join the organization. This works for new users only.
Simply enter your District ID here and instruct your users to sign in with their Clever account.
G Suite Login and Google Classroom integration: use the 'Enable' button if you'd like to enable Google SSO and its advanced version. You can learn more about both here. Note that you need to log in with your Google account in order to see these options.
LTI 1.3 connections: ThingLink's LTI 1.3 app allows you to easily embed ThingLink content into your LMS and send data from scenarios back to LMS. See this article for more information.
LTI 1.1 can be used to set up a simple button that will allow your users to access ThingLink using their LMS account credentials. See this article for more information.
This section allows you to check and control your organization name, subscription information, views and seats.
Additional user invitation options
Teacher invitation code or User invitation code is the default invitation code for your organization. Your colleagues who already have an account can use it to join your organization. Click here to learn more about invitation codes and how they can be used.
Note that this code cannot be used by students.
Email domains: you can limit who can join your organization via an invite code by whitelisting certain domains. If this field is empty then any user can join. We recommend using this setting if you want to ensure that all your colleagues or students are signing up with their work/school accounts.
Note that this setting has to be changed by ThingLink staff. Please contact firstname.lastname@example.org if you wish to change it.
This section contains different settings that are shared for all users in your organization, such as interface version, default language and a few others.
Legacy editor setting allows you to either enable or disable the legacy editor for all users in your organization. If the legacy editor has been enabled, you'll see a number of related settings appear.
All users in an organization will always have the same editor version. It is not possible to enable the legacy editor for select team or school members. We do not recommend using the legacy editor.
Interface version: allows you to change between Saimaa (2020) and Ruovesi (2017) interface versions. The interface version is shared between all members of the organization to ensure consistency.
Interface language allows you to control the default interface language for new users. Once logged in, the user can select a different language. Note that for some languages, only the editor interface has been translated. You can learn more about the available languages here.
Default content visibility setting allows you to control the default visibility setting for content created by members of your organization.
Level of support allows you to choose which part of the ThingLink's support team can access your user's data.