Skip to Content
Distributing contentDistribution

Understanding distribution

Distributing, in Beedeez, means deciding who has access to what. Three models do it, they combine, and the choice comes before any screen: it sets the upkeep you carry afterwards, distribution after distribution.

On this page

Understanding distribution

Distributing, in Beedeez, means deciding who has access to what. Three models do it, they combine, and the choice comes before any screen: it sets the upkeep you carry afterwards, distribution after distribution.

Choose the model before the screen

The three models do not ask for the same upkeep.

Making content available to the whole account costs nothing to maintain: nobody is targeted, so nothing goes stale when the population changes. In exchange, you will not know who read it, and you can neither follow up nor make the content mandatory.

Distributing through tracks means keeping groups and tracks up to date. That is the price of tracking: it is the only model that lets you target an audience, measure completion and expect something from the learner. When in doubt, take that one.

Customising a capsule for specific groups costs almost nothing to set up and is paid at diagnosis time: two learners on the same track can then legitimately see different things, and you have to remember it every time someone reports an oddity.

The four pages in this section

  1. Model 2: distribution through tracks: start here. It is the default model, and it carries the rule behind almost every case where a learner does not see what you believe you gave them.
  2. Model 1: global distribution: read this when deciding in advance who will need the content makes no sense, for a procedure or a product card people look up when the question comes up.
  3. Model 3: custom diffusion per group: read this when one capsule has to be mandatory here and informational there. It opens access to nobody, it refines access already granted.
  4. Who can distribute what: the rights that decide what each person can distribute, and the first place to look when a button is missing from the screen.

A department is not a fourth model

A department is a scope, and it applies to all three models. Permissions say what a person can do, the department says what they do it on. Each department has its own content, groups and tracks, a group belongs to exactly one of them, and you distribute inside it exactly as you would anywhere else. See Understanding structure and permissions and Modelling your organisation.

And when everything looks set but the learner still sees nothing: Common problems: distribution.


Discutez avec nous