RELATED IDEAS
Code-like configuration for workspaces
Setting up multiple workspaces is a chore. Aha! provides a range of shared definitions (layouts, etc) that make it easier to maintain consistency in some areas, but these fall down in two ways. Firstly, they're not universal, they don't exist for all aspect of a workspace behaviour, and secondly, they don't help much when a workspace is almost-but-not-quite-identical. For example, integration templates for JIRA integrations require all record and field mappings to be identical, otherwise you have to start from scratch and manually reproduce the integration from one workspace to the next, just to accommodate maybe one field mapping that is different.
A powerful way to address this problem would be to allow workspace configurations to be defined and edited as code - for example, if everything were defined in an XML document it would be much easier to cut-and-paste parts of configuration between workspaces and modify just the one or two elements that need to be changed.
This would also be a big help in managing and auditing configuration.
-
ADMIN RESPONSEMay 18, 2022
Create custom workspace templates
Standardize the way you set up new workspaces so teams follow the same approach. Create a template with predefined workflow statuses, custom fields, automations, and more. This update is available for customers on our Enterprise+ plan.
Checkout the blog post for more details.
