Use case - Fluid Topics - Latest

Fluid Topics Configuration and Administration Guide

Category
Reference Guides
Audience
public
Version
Latest

In this use case, two companies named Acme and Lumon have access to different topics in a document which is exclusively destined to them. The document plan is as follows:

  • Document (Acme & Lumon)
    • Topic A (Acme)
      • Topic A1
    • Topic B (Lumon)
      • Topic B2
    • Topic C (Acme & Lumon)

To implement this plan:

  1. At the document level, create an access rule to restrict access to the groups Acme and Lumon.
  2. Create a rule based on a metadata value that is unique to topic A to only grant access to users in the Acme group.

    Acme users also get access to topic A1.

  3. Create a rule based on a metadata value that is unique to topic B to only grant access to users in the Lumon group.

    Lumon users also get access to topic B2.

  4. Create a rule based on a metadata value that is unique to topic C to only grant access to users in both the Acme and the Lumon group.

  • Although it would possible to give access to topic B2 to Acme, or both Lumon and Acme, by creating a new rule, it is not recommended practice. In such a use case, the parent topic would not be readable, and would show an error message.
  • If there were a Topic D meant for another company, they could not access it since they are not authorized to access the document in the first place.