Summary

This feature set is still being defined.

The problems we’re solving

1. It’s difficult to reliably reproduce behaviors that are specific to certain production tenants, given the number of potential configurations within a given tenant / knapsack

2. It’s challenging to automate testing with certain datasets where associated behaviors and workflows are enabled / dependent on tenant-specific configurations

3. It’s somewhat time-consuming and expensive for new Hyku user organizations to get their tenant looking and feeling mature and “premium”.

The objectives

• enable new organizations to import a “jumping off point” - a fully-functional, mature tenant or organization’s configuration

• enable testing of tenant-specific behaviors / reproduce tenant-specific bugs

• lay the groundwork for improved test automation with key testing tenant configurations + datasets (and known configurations)

Flavors of the feature set

Imagine: Export button, then checkboxes for each item / collection of items

1. Biggest: Full tenant portability

   1. Collections + Works

      1. PostgreSQL DB

      2. S3 objects

   2. Users

   3. Configurations

   4. Customizations

      1. Custom styling / themes

      2. Metadata configs

      3. Admin sets, roles, permissions

      4. Settings / feature flags

2. Medium

   1. Users + Roles

3. Smallest: Account itself

   1. Config

   2. SSO