Configure Applications for student use
Outcome You set application configuration (inactivity limit, shared mode, resources) and distribute the configuration to all students at once.
Before you start
You are a Space Administrator of the course.
The application exists in the Master Instance.
Space Administrators can configure student applications in two ways:
Per application, per instance - configure through the web UI. Affects only that application in that instance.
Via distribution - configure the application in the Master Instance, then distribute it. Configuration is included with the distribution and applied to every student application.
When distributing applications in course spaces, three configuration values are particularly important and travel with the application:
Inactivity limit - how long the application stays running without student interaction.
Shared mode - whether multiple users connect to the same running application.
Resource settings (size) - how many NCUs the application uses.
For all configurable options and their effects, see Reference › Applications.
Last updated
Was this helpful?