A module can be switched on for your organisation and still switched off for particular tribes. That is how you pilot something at three tribes before giving it to fifty.
Two levels
| Level | Effect |
|---|---|
| Organisation | Whether the module exists for you at all, and whether tribes can have it. |
| Per tribe | Whether each individual tribe has it. |
Both have to allow it. Switching a module on for one tribe will do nothing if it is off for the organisation.
It works by exception
For a genuine pilot, use the module's own tribe access screen — CRM has one, for instance — where Enable for all tribes, Select all and Deselect all let you set the whole network in one go and then re-enable the handful you want.
What a tribe sees when it is off
The module disappears from that tribe's menu, and anybody who reaches a page inside it directly is told the module is disabled for their tribe. It is not a permission error and giving them more permissions will not help.
Remember it when you open a tribe
A new tribe inherits everything by default, which is usually right and occasionally not. If your pilot module should stay limited, switch the new tribe off as part of opening it — otherwise it quietly joins the pilot.
Turning something off does not delete anything
The tribe's data in that module stays exactly where it is and comes back when you switch it on again. It is a visibility change, not a removal.