Managing Workspaces & Orgs10% of the exam
Personal Org (Exploratory Org) setup and ownership
How admins enable, create, staff and delete Personal Orgs (now Exploratory Orgs), the limits on how many can exist and who can own them, what analysts can reuse from production, and what owners, Editors and Viewers can do in a shared workspace.
Understand how to deploy and manage a Personal Org.
~7 min read · 11 practice questions
What the exam expects
- Enable the Personal Org (now Exploratory Org) feature and create an org for one or more analysts.
- Plan how many orgs an org can have, who can own one, and what owners experience after creation.
- Explain admin ownership, license loss and safe offboarding (promote, then delete).
- Predict what an analyst can reuse from production and what stays locked.
- Share a workspace in an Exploratory Org and tell owner, Editor and Viewer capabilities apart.
Key terms:
- Personal Org (Exploratory Org): an isolated Tableau Next environment where analysts combine corporate data with their own datasets; Help now titles it Exploratory Org.
- Production org: the managed, governed Tableau Next environment where finalized, approved content lives.
- Owner: a user with full access to every asset in an Exploratory Org; an org can have several.
- Reused asset: a production asset added to an Exploratory Org workspace through Add Existing.
- Promotion: moving finished assets from an Exploratory Org into production.
Key facts
Enable the feature
- Detail
- Tableau Next Features, Exploratory Org; Tableau Next Admin set
Create an org
- Detail
- Users, the user's Exploratory Org tab, Create Exploratory Org
Maximum orgs
- Detail
- Lower of 100 or the number of Creator licenses
Owners
- Detail
- One or more, same access; admins always owners and can't be removed
Creation time
- Detail
- Up to an hour; welcome email to each owner
License lost
- Detail
- Owner loses access; reassigning the license restores it
Deletion
- Detail
- Permanent; all content deleted
Data space
- Detail
- Default data space only
Reused DMO
- Detail
- Needs a production DLO mapping; locked, blend with local data
Sharing
- Detail
- Workspace level only; Viewer or Editor
Sources for this section (6)
- Enable Exploratory Orgshelp.salesforce.com (opens in a new tab)
- Create an Exploratory Orghelp.salesforce.com (opens in a new tab)
- Tableau Next Exploratory Orghelp.salesforce.com (opens in a new tab)
- Delete an Exploratory Orghelp.salesforce.com (opens in a new tab)
- Reuse Production Org Assetshelp.salesforce.com (opens in a new tab)
- Capabilitieshelp.salesforce.com (opens in a new tab)
- When a reused production asset is deleted at its source, what happens in the Exploratory Org and who cleans up?
- Why might a colleague opening a shared Exploratory Org workspace see fewer assets than its owner?
- Which filters help an analyst find a production asset under Add Existing?
- How can an admin let Salesforce Support investigate a problem inside an Exploratory Org?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Tableau Next Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 21 lessons of the Tableau Next Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (11 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both