Ideas

Would be very helpful to be able to create Roles and modify permissions through an API so developers can script roles and apply them across spaces and environments. At the moment, every time a new "model" is added, we have to manually go in and se...

People don’t think linearly. In creative or technical tasks, thoughts emerge unpredictably—you recall a feature you need, a bug to fix, or a UI detail while working on something else. A chat queue allows users to quickly offload ideas without losi...

It would be great if you could add the "allow-storage-access-by-user-activation" token to the live editor's iframe. This feature would enable several valuable use cases, and I'll describe my specific situation below. We recently implemented Next.j...

For the purpose of restricting certain fields in a data model from being edited by any user, I should be able to target the current user's role in a validation hook. Something like async function run ( ) { if (context.user.role != 'admin' ) { retu...

It is not possible to specify anything else than objects as children for list input type.

It is useful sometimes when you create a project to duplicate it and make changes to both of them from different perspectives to make A/B testings for example.

It would be very useful to have access to queryParams in the toUrl function when building custom plugins. We are building a plugin that uses personalization that usually we include as queryParams so that users can change their state in the UI to t...

With a multii site scenario there is a common need to share model definitions across spaces. Currently to synchronize model definitions across spaces you need to write code using the Admin SDK. There really should be admin features within the app ...

Would be great to add the ability to folder, filter, and/or organize users based on role, department, or misc. within the main Account Settings list. Ex. Even if you have users that are associated with different Spaces (Ent), they may be a part of...

I want to query content items using the query syntax but manipulate the set of returned items based on certain conditions. My main use case is that I want to query for a URL path and a custom targeting attribute. If there's a content item for that...