Currently, our solution to this is to manually cross-post topics to both a group and a class, so that they are findable in both topic bank domains. Which means we have either a shell group (or a shell class) whose sole purpose is to hold topics so that other groups (or courses) can see them.
I could imagine optionally restricting a topic to one or the other bank, but certainly having the option to share across that boundary would be huge.
Currently, our solution to this is to manually cross-post topics to both a group and a class, so that they are findable in both topic bank domains. Which means we have either a shell group (or a shell class) whose sole purpose is to hold topics so that other groups (or courses) can see them.
I could imagine optionally restricting a topic to one or the other bank, but certainly having the option to share across that boundary would be huge.
Please change