Hi Sam -
Tableau Server does no site-specific resource governing above and beyond (very) basic data size & user count limts. You can't tell it to "only let site X use up to 25% of the CPU or RAM", which I think is what you're after.
Lots of people use the approach you're considering. In fact, that's the whole reason why Tableau created the Site Admin. Generally, the System Administrators do what you envision, except that they also look out for "rogue workbooks and jobs" that run for an unreasonable amount of time and soak up too many resources. When you spot those, it becomes the site administrator's responsibility to deal with (or remove) them.
(Don't get me wrong on this next part). What you're considering is not a big deal or at all out of the ordinary: It's a pretty basic and well known approach (that's good news).
I second Russell's reply.
I only have four Sites that are used by other departments. Each Site has two Site Admins minimum (four would be our maximum) and they are very proficient with Desktop. I love it. They take care of their own stuff which, basically, gives me time back. Now the only Site I really only have to deal with is the Default one.
Segregating functional groups into different sites is definitely handy from
a self service point of view.
The caution I have is that if there would ever be a need to share a
published datasource between groups you can't do it with this approach.
Same goes for user groups, projects, user permissions, etc. All of that
stuff has to be duplicated between sites should you need to leverage any of
On Mar 16, 2017 12:00 PM, "Toby Erkson" <email@example.com>
Eric, correct, good point! Our data is highly silo'd and even those that use the same data source don't use the same data (different tables and/or columns) so we aren't affected by that.