Temp Tenant Types: When to Use Demo vs. Test as a Partner?

I am trying to understand the difference between demo and test temporary tenants, and after reading through Help and looking through Community I still have some questions.

  1. What is the demo tenant used for? I saw this post that suggests most people should use the test tenant. But I am not sure where that leaves the demo tenant?
  2. Which tenant type should a partner use to demo their own features? Is the demo tenant only for showcasing platform features, or is it also appropriate for partners demoing their own solutions?
  3. What does it mean that “demo tenants copy everything”? I saw a reference to this in the post linked above and I’m not sure what it means in practice. Does that mean you don’t need to specify any tables and it will pull all data from your seed environment automatically?
  4. What’s the difference between “Tables to Migrate” (Test) and “Platform Tables to Migrate” (Demo)? On the Temporary Tenant Template Setup for a test tenant, there’s a “Tables to Migrate” field. On the demo version, it’s “Platform Tables to Migrate.” Does that mean demo tenants can only copy platform tables, and not partner-built tables?

Thank you!

  1. Demo tenants are primarily used internally for Demos. They are often longer lived, and have and handful of additional bells and whistles that test tenants do not.
  2. Partners can use either type for demos, it just depends on whether or not they need some of the extras that demo tenants provide.
  3. Yes, Demo tenants automatically copy all business data tables from their seed environment. This often makes them take longer to spin up. Test tenants only copy the set of tables specified on the Template record.
  4. This is one of the extra features that Demo Tenants provide. The mechanism for migrating business data into Temporary Tenants is Quick Start, which automatically filters out platform families. So if the temp tenant needs to copy over any such table, you need a demo tenant.

Additional Demo Tenant Features

  1. Set a custom expiration date
  2. Provide a list of custom usernames