Absolutely! There is only one gotcha: You will probably want to setup SAML for SSO, since Trusted Tickets are not supported by Tableau Online.
Check out the security tab on the left for more info on SAML setup.
Yes! You can pull dashboards from multiple sites, however, the master user in the backend of the Portal must be at least a Site admin on both sites (Server admin is preferred for multi-site setups).
This is required so that permissions can be checked for the users logging into the frontend.
Somewhat! You can pull dashboards from multiple servers, however, the permissions and login come from a master Tableau Server.
You can use groups from the master Tableau Server to drive who can see the links for the secondary Tableau Server.
In many cases, a secondary Portal might make more sense.
Of course! The Portal is mobile friendly out of the box and adjusts the layout in a responsive format.
Of course, your Tableau dashboards will need to be configured to be mobile friendly as well! You can do this using the Tableau 10+ mobile functionality or by providing a secondary dashboard to display on mobile devices.
We actively support the latest versions of these browsers:
Some older browsers may not be fully compatible with the Portal, so make sure you're using the latest version of one of these browsers.
All hosting solutions allow for a custom domain! Most clients use a domain like reports.clientname.com or data.clientname.com, but the Portal location is totally up to you!
Out of the box, the Portal tracks some basic information about users' dashboard loads.
We highly recommend, however, adding a more advanced analytics system such as Google Analytics or Matomo (Piwik).
These free systems are built for advanced analytics of user's behavior.
To connect your Portal, simply plug in your account information in the Portal Settings area.
Yes! The Portal can be customized in some ways based on the user's groups in Tableau Server.
For more information, please see our blog on this topic here.
Yes! The Portal allows you to continue using these URL actions. We do have some recommendations, though. You can view those here.
Woah, there! Are you sure we don't support that out of the box?
If you are sure, then we do have safe areas for customization!
These areas will remain intact during Portal upgrades.
For dashboard specific upgrades, use "Content->Dashboards->Edit Dashboard->Header"
For custom pages, use "Content->Pages"
For Portal-wide customization, use "Settings->Portal Settings->Styles"
Absolutely! We have a couple of different installation options. Our most seamless offering is to host the Portal for you. This requires no setup - just let us know you want us to host the Portal and we'll take care of the details for you!
Of course, we can also help you install the Portal on your cloud hosted hardware, or if you prefer, on your premise hardware.
You bet it does! For more information on this type of setup, please see our High Availability setup guide.
This is not recommended, but technically possible. If you use this route, you cannot use SSL and your Tableau Server or Portal will have to run on a non-standard port.
It's most optimal to run a Portal on Linux, but we can easily host on Windows as well. We recommend a stand-alone server (aka, not running any other major applications), and at least 2 CPU, 4GB RAM, ~20GB of Disk Space (if using Windows Server, 4 CPU/8 GB RAM). For more information on requirements, check out our requirements page.
Other than well documented monetary, stability, and security reasons to choose Linux, there is a significant speed increase using the Portal software on Linux systems. Besides simply being a lighter operating system, Linux allows us to access an extra memory based caching layer which really makes your Portal zoom!
No Linux experience? That's fine - the Portal works fine on Windows as well!
For backend processing, the Portal uses PHP with a database backend. (PHP 7+ required)
For frontend styling, the Portal use Bootstrap 3.
The Portal uses a database for small backend configuration settings only. It does not store any of your workbook data.
The Portal uses a database for small backend configuration settings. The database software can vary, depending on client needs:
SQL Server will need the Group Concat function installed, you can find it here.
The cron runs any scheduled processes on the Portal system, such as syncs with Tableau Server, cache maintenance, and more.
You’ll want to run the process every minute, but it doesn’t “do” something every minute: just if something is scheduled.
You will need one license per Portal installation. Each license also allows you one 'dev' installation for testing purposes.
The Portal does track user dashboard visits; however, we'd recommend a more advanced system such as Google Analytics or Matomo, which are easy to setup in the backend of the Portal.
Yes, but with some stipulations!
The Portal supports SAML, and most SAML vendors support dual factor authentication.
Check with your SAML vendor to determine if they support this functionality.
If you are using SAML and your SAML vendor supports dual factor authentication, it can also be used in the Portal.
Trusted tickets allow the Portal to authenticate your users automatically in the Tableau Server environment. Setting up Trusted authentication requires a minor change on the configuration of Tableau Server. You can do this with tabadmin on the Tableau Server box.
First, collect the IP Address(es) of your Portal server. (If you don't know this - ask your InterWorks Portal contact)
Next, connect to your Tableau Server box and open a command prompt and navigate to your Tableau Server "bin" directory. (for example, C:\Program Files\Tableau\Tableau Server\10.5\bin)
Finally, run the following commands:
tabadmin set wgserver.trusted_hosts "
" (comma separated, if multiple)
For more information, see Tableau's documentation.
First, make sure you completed the Trusted Ticket setup above!
If that doesn't work, your Tableau Server is not being accessed directly by the Portal.
If you can route the REST API calls through internal routes, use the Alternative Server URL setup in the Portal's Tableau Server Settings section to do so. (This allows you to route Portal server-side requests over one URL and client requests over another.)
If you can't route the REST API calls through a more direct route, you'll need to debug the IP address Tableau Server is seeing.
First, connect to your Tableau Server box and open a command prompt and navigate to your Tableau Server "bin" directory. (for example, C:\Program Files\Tableau\Tableau Server\10.5\bin)
Next, run the following commands:
tabadmin set vizqlserver.trustedticket.log_level debug
After the Tableau Server has restarted, hit a dashboard on the Portal a few times. Note: You will still see an error! This is expected!
Finally, grab the logs and look for "Trusted" near the bottom of the file. It will list any missing IP Addresses requested trusted tickets.
To easily collect your logs, use the following command and then look for vizql-*.log files:
tabadmin ziplogs C:\mylogs.zip
For more information, see Tableau's documentation.