Absolutely! There is only one gotcha: You will probably want to set up SAML for SSO since Trusted Tickets are not supported by Tableau Online.
Check out the security SAML FAQ ifor more info on SAML setup.
You can pull dashboards from multiple sites; however, the master user in the backend of the Curator site must be at least a Site admin on both sites (Server admin is preferred for multi-site
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! Curator 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
We actively support the latest versions of these browsers:
Some older browsers may not be fully compatible with Curator, 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 location is totally up to you!
Out of the box, Curator 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 users’ behavior. To
connect your portal, simply plug in your account information in the Curator Settings area.
Yes! Curator 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! Curator 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 upgrades.
For dashboard-specific upgrades, use "Content->Dashboards->Edit Dashboard->Header"
Absolutely! We have a couple of different installation options. Our most seamless offering is to host Curator for you. This requires no setup - just let us know you want us to host Curator and
take care of the
details for you!
Of course, we can also help you install Curator on your cloud-hosted hardware or, if you prefer, on your on-prem hardware.
Absolutely! InterWorks hosting your Portal is the most seamless option. However, we understand that you may want to host this somewhere that's not reachable from the public internet.
In that case, we can take care of the hosting and OS maintenance wherever your Server lives with ServerCare by
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 (a.k.a. not running any other major applications) and at least 2 CPU, 4GB RAM, ~20GB
(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 running Curator 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 - Curator works fine on Windows as well!
For backend processing, Curator uses PHP with a database backend. (PHP 7+ required)
For frontend style, Curator uses Bootstrap 3.
Curator uses a database for small backend configuration settings only. It does not store any of your workbook data.
Curator uses a small database for backend configuration settings. For this database, we use an embedded MariaDB instance.
The cron runs any scheduled processes on the Curator 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.
We are always looking for ways to add new features and improve the ones we’ve already created. Please let us know if you have a great idea and we’ll discuss the possibilities with our development team.
make sure to keep you in the loop on the exciting new features that are just around the corner!
Product updates are released frequently. These updates keep your application up-to-date with the latest analytic platform features but also introduce new features of our own.
Curator does track user dashboard visits; however, we'd recommend a more advanced system such as Google Analytics or Matomo, which are easy to set up in the backend of your Curator site.
Yes! We have documentation on Okta and OneLogin, but other SAML vendors are supported as well.
Yes, but with some stipulations!Curator 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 Curator.
Trusted tickets allow Curator to authenticate your users automatically in the Tableau Server environment. Setting up Trusted authentication requires a minor change on the configuration of Tableau
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, open a command prompt and navigate to your Tableau Server "bin" directory. (i.e. C:\Program Files\Tableau\Tableau Server\\bin)
Finally, run the following commands:
tsm authentication trusted configure -th
tsm pending-changes apply
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 Curator.
If you can route the REST API calls through internal routes, use the Alternative Server URL setup in Curator'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.
Next, connect to your Tableau Server box, open a command prompt and navigate to your Tableau Server "bin" directory. (for example, C:\Program Files\Tableau\Tableau Server\\bin)
Next, run the following commands:
tsm configuration set -k backgrounder.native_api.log.level -v debug
tsm configuration set -k vizqlserver.log.level -v warn
tsm configuration set -k vizportal.log.level -v debug
After the Tableau Server has restarted, hit a dashboard on Curator 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 requesting Trusted Tickets.
To easily collect your logs, use the following command and then look for vizql-*.log files:
tsm maintenance ziplogs C:\mylogs.zip
Definitely. We take your data security seriously, so we've provided built-in security that connects to your Tableau Server for each menu item. What does that mean exactly?
If the user doesn't have access to a dashboard on Tableau, they won't see it in the menu.
We've also got more options for customizing security on each of your dashboards. You can find more info on that in our documentation on our Resources page.