Sites and projects
The structure as it stands, including the content nobody has claimed.
Govern Tableau Server, on your own infrastructure
The same governed tools and the same approval gates. You can run the whole product inside your own cloud. Your organisation holds the Super Admin account.
Run it where the data already is
The perpetual edition runs on your own infrastructure, and your data stays there. It is the same product as the hosted edition.
- The same product on either edition, never a stripped-down one
- Your organisation holds the Super Admin account
- Your data stays on your own infrastructure
- If you do move to Tableau Cloud later, that has its own path and its own page
You can see what the Server is doing
Tableau Server keeps its own logs. Log reads them into one deck you can search, filter and export.
- Four capture sources, each labelled honestly when your license or edition cannot offer it
- Eight severity levels, and a Log Explorer with four lenses
- Five export formats for the evidence you hand to somebody else
Evidence an auditor already recognises
Run the infrastructure yourself and the security posture is yours to show. Guard tags what it finds against published control catalogues. A finding arrives with its control reference already on it.
- Every finding carries a CIS Controls v8.1 Safeguard ID and a NIST CSF 2.0 function
- That tag travels into the CSV, the SARIF 2.1.0 export and the PDF unchanged
- Mapped audit evidence, stated plainly as that. It is not a certification of compliance
What it reads
Permissions and identity
Who can reach what, who owns it, and what changes when a person leaves.
Schedules and subscriptions
The work Tableau Server does on its own, listed with the people it belongs to.
Server logs
What happened, from the sources your edition exposes.