Totara Learn Open Discussions

Workspaces - hide Discussions/ Members tabs

 
HansenMonica
Workspaces - hide Discussions/ Members tabs
HansenMonica 发表于 2026年02月5日 Thursday 02:30
 

Hi everyone,


Our team is currently exploring the use of Workspaces as a structured way to bundle and present our learning offerings. The setup looks very promising so far :)

One question we’re looking into: Is there a way to disable the Discussion and Members tabs for scenarios where interaction isn’t needed or where a content‑only experience would be preferable?


If anyone has experience with this or knows whether it’s configurable, we’d appreciate your insights.

Thanks in advance!


All the best,

Monica.

AloziePierre
Re: Workspaces - hide Discussions/ Members tabs
AloziePierre 发表于 2026年02月6日 Friday 01:54
 

Hi Monica,

We have been using Workspaces for 2 years (cohorts) now and we have just implemented it for 6 more courses.

The workspace was used as supplementary spaces for the cohorts, but this time they are now the main space for the students to be in.

All their resources are there and if we need any activities only found on the course pages, they are created and linked back to the workspace. The advantage of that is that the recourses for the student appear in the library

With all that we have not found a way to hide the discussion tab, but in any case, we use it for the students and tutors to communicate. One could possibly use CSS "custom code" in totara to hide the tab.

Peace

Pierre

标签:
HansenMonica
Re: Workspaces - hide Discussions/ Members tabs
HansenMonica 发表于 2026年03月3日 Tuesday 07:57
 

Hi Pierre,

Thanks so much for sharing your experience— that’s really useful!

It’s great to hear how you’ve been using Workspaces, sounds like a smart setup for keeping everything in place for your students. We're also excited to launch them soon, and it's good to know it works well in practice.

Also appreciate the confirmation that the Discussion tab can’t currently be disabled natively. We had a similar thought about possibly using custom CSS if we decide we need a purely content‑only experience in some cases — we'll keep this in mind.

Thanks again for taking the time to explain how you’ve approached it.


Kind regards,

Monica.