Moodle Workplace Test3: Difference between revisions
No edit summary |
No edit summary |
||
| Line 24: | Line 24: | ||
*Placing programs in shared space | *Placing programs in shared space | ||
===Sharing courses across tenants=== | ===Sharing courses across tenants=== | ||
By default, neither the Tenant | By default, neither the Tenant Administrator nor the Programs Manager can see courses outside their own tenant's course category when adding courses to programs. However, the site can be configured to allow a '''Shared''' course category to override permissions, enabling users to browse courses from other tenants. Alternatively, a specific user can be designated to create programs for different tenants and granted access to all courses. This setup allows the same course to be added to different programs belonging to various tenants. | ||
To grant | To grant the permission to add courses to a program outside their own tenant's course category, you need to assign the '''moodle/category:viewcourselist''' capability at the category context. The handling of programs will remain the same, so program managers must be vigilant when arranging courses in programs from different tenants. | ||
If a course has been set up using | If a course has been set up using '''Separate Groups''', an attention icon will be displayed. Users will be enrolled in the same course but will not be able to see each other. If the course is configured with '''Visible Groups''' or '''No Groups''', the attention icon will appear next to courses that do not belong to the current tenant's course category. Users from one tenant will be able to see users from other tenants, for example, in the participants’ list or collaborative activities such as forums. Therefore, it is highly recommended to have all shared courses in [[Groups#Group modes|'''Separate groups''']] mode and to enforce group mode for all activities. | ||
The Programs enrolment method will always allocate users from different tenants into different groups. | The '''Programs enrolment method''' will always allocate users from different tenants into different groups. These groups will be created automatically based on the name of the tenant and can be manually renamed later without affecting the allocation of future students. | ||
===Programs in shared space=== | ===Programs in shared space=== | ||
After enabling Shared space, administrators can create shared programs inside of it. These shared programs will be listed on the '''Programs''' main page in all tenants and marked with a '''Shared space''' label next to it. Users from these tenants with no access to the Shared space will be only able to allocate users to these programs. | After enabling '''[[Shared space]]''', administrators can create shared programs inside of it. These shared programs will be listed on the '''Programs''' main page in all tenants and marked with a '''Shared space''' label next to it. Users from these tenants with no access to the Shared space will be only able to allocate users to these programs. | ||
[[File:Programs - Shared space.png|border|center|frameless|900x900px|alt=]] | [[File:Programs - Shared space.png|border|center|frameless|900x900px|alt=]] | ||
The range of actions has been restricted to program duplication, user allocation, and accessing the program report. All other actions can only be performed when you manage the program from within the shared space. | The range of actions has been restricted to program duplication, user allocation, and accessing the program report. All other actions can only be performed when you manage the program from within the shared space. | ||
Revision as of 10:43, 19 March 2025
|
|---|
| Overview | Configuration | Use cases | Tenants | Technical |
|---|
Sharing content across tenants
Moodle Workplace offers two ways to share content across tenants via programs:
- Sharing courses across tenants in a single program
- Placing programs in shared space
Sharing courses across tenants
By default, neither the Tenant Administrator nor the Programs Manager can see courses outside their own tenant's course category when adding courses to programs. However, the site can be configured to allow a Shared course category to override permissions, enabling users to browse courses from other tenants. Alternatively, a specific user can be designated to create programs for different tenants and granted access to all courses. This setup allows the same course to be added to different programs belonging to various tenants.
To grant the permission to add courses to a program outside their own tenant's course category, you need to assign the moodle/category:viewcourselist capability at the category context. The handling of programs will remain the same, so program managers must be vigilant when arranging courses in programs from different tenants.
If a course has been set up using Separate Groups, an attention icon will be displayed. Users will be enrolled in the same course but will not be able to see each other. If the course is configured with Visible Groups or No Groups, the attention icon will appear next to courses that do not belong to the current tenant's course category. Users from one tenant will be able to see users from other tenants, for example, in the participants’ list or collaborative activities such as forums. Therefore, it is highly recommended to have all shared courses in Separate groups mode and to enforce group mode for all activities.
The Programs enrolment method will always allocate users from different tenants into different groups. These groups will be created automatically based on the name of the tenant and can be manually renamed later without affecting the allocation of future students.
After enabling Shared space, administrators can create shared programs inside of it. These shared programs will be listed on the Programs main page in all tenants and marked with a Shared space label next to it. Users from these tenants with no access to the Shared space will be only able to allocate users to these programs.
The range of actions has been restricted to program duplication, user allocation, and accessing the program report. All other actions can only be performed when you manage the program from within the shared space.
