What is the best practice to share business-facing content with business users?

Ikhwanul
Ikhwanul Registered Posts: 2 ✭✭

My team has developed several Dataiku Apps and Dashboards that are ready to be shared with business users. Currently, I am considering the following approach:

  • Deploy the content from Designer to the Production Automation node.
  • Share the Dataiku Apps and Dashboards through specific workspaces.

I am wondering:

  • Is it common to organize these workspaces by business department, or is there a better structure?
  • Are there alternative or recommended best practices to make this content easily accessible to business users?

Operating system used: RedHat 7.9

Answers

  • Islam
    Islam Dataiku DSS Core Designer, Registered Posts: 14 ✭✭✭✭

    Hi Ikhwanul,

    From experience, what works best is to avoid multiplying workspaces by department. That becomes heavy to maintain. Instead, we keep transversal workspaces and rely on a combination of project/content tags and naming standards so business users can easily navigate. For example, tags like Finance, Risk, Marketing make it straightforward to filter and find the right apps or dashboards.

    Personally, I also prefer to manage access at the group level, not user by user. Roles and groups are mapped early (e.g., Analysts, ML Engineers, Ops, or by specific domain like “Report-about-Sales”), and permissions are injected via templates when projects are created. This avoids “privilege creep” and ensures only the right people see the right data when content is promoted to Automation.

    On top of that, we enforce metadata and tagging practices - every project and dataset gets an Owner, Sensitivity, and Business Domain tag. This keeps the catalog clear and makes governance reporting easier.

    Finally, validated bundles only are promoted to Automation, and we maintain a central usage guide with direct links to the apps/dashboards. Business users see a single entry point, but behind it, tags, groups, and templates keep things clean and secure.

    Do you want me to adapt this into a concrete example with a simple layout of domains, tags, and groups so you can reuse it with your team?

    BR

    IO

  • Ikhwanul
    Ikhwanul Registered Posts: 2 ✭✭

    Hi IO,

    Thanks a lot for your detailed input, this is very helpful.

    • I fully agree with your point that content promoted to the Automation node should only come from validated bundles. That makes a lot of sense in terms of governance and quality control.
    • Regarding the idea that organizing workspaces by department can become heavy to maintain, I don’t fully grasp what kind of challenges you’ve experienced in practice. Could you please elaborate a bit more on what tends to get complicated (e.g., permissions, content duplication, navigation, etc.)?
    • Lastly, yes, I’d really appreciate if you could share a concrete example of how you’ve structured domains, tags, and groups in a simple layout. I think that would help me translate the concept into something my team can directly reuse.

    Cheers,
    Ikhwanul

Setup Info
    Tags
      Help me…