Like what you see? Have a play with our trial version.


Yellowfin has functionality called Client Organisations which allows multiple virtual instances of Yellowfin to reside in the same server instance. This provides a way to create content isolated within one organisation, hidden from other organisation users logging into the same server.

Client Orgs is a two-tier structure. The top tier, known as the Primary Org (default), can have content that is shared with all Client Orgs. Content created at the Client tier, however, will be private.

In a standard installation of Yellowfin, there are initially no clients, just the default tier. A Client Organisation is identified by a Client Reference ID, which is a unique text identifier assigned when the client is created. Yellowfin can use this ID as an Access Filter.

See Initial Setup and Content Management for more information.


Content such as Data Sources, Reports, and Dashboards belong to either the Primary Org or a single Client Org. The owner of the content is determined by the Org (Primary or Client) it is created in.

Content that belongs to the Primary Org will also be visible to the Client Org tier, allowing the same content to be used across multiple clients.


Users can be assigned access to the Primary Org, and/or one or more Client Orgs, but may only ever be logged into a single Org at a time. Groups can also be used across both tiers and multiple orgs. When managing users through Administration, you will only ever see users that have access to the Current Org (currently logged in to). For example, if you're logged into the Primary Org, you will only see users that also have access to the Primary Org.

A user's role follows them across all Orgs they have been granted access to. For example, if a user is given an Administrator role, they will have access to the corresponding functionality at any clients they have access to.


The Configuration and Report Styles pages are available in both Primary and Client Orgs to users with appropriate role permissions. The configuration settings applied at the client are exclusive to that client, much like their content, meaning that each client can be configured and styled differently. This allows for different region, integration, and style settings across clients.