Lindy Community Icon

Best Practices for Multi-Client Knowledge Bases Explained

ยท
ยท

What are best practices for knowledge bases when you have multiple clients? For instance, let's say I want to write blog posts for different clients. Is it best to have one "Blog Post Writer" Lindy with different paths that contains for each client or a Lindy that has a step to talk to another Lindy that contains the particular client's knowledge base? If so, how do you do that? I would think it's best to have a dedicated knowledge base (as a separate Lindy), so you can talk to it in many different automations.

  • Avatar of Aaron E.
    Aaron E.
    ยท
    ยท

    David W. Not sure the โ€œrightโ€ approach, but what comes to mind for me is putting your company KB into a sub-flow and calling it from a flow you create for each client. The flows you create for each client could be templated so that they can be re-used and also customized for each client. Iโ€™m assuming all of this is on the same Lindy account, but I suppose you could also do it across accounts if needed.

  • Avatar of Marvin A.
    Marvin A.
    ยท
    ยท

    Agreeing with Aaron on this. ๐Ÿ‘† Great suggestion.