March 5, 2026 / 🙈 Hide Entity Views with rules, Specify which Entity View to open by default for a user, Validation rules on Create

This is huge! Looking forward to simplifying my entity views for users. Thanks team!

Also useful - a few times I’ve wanted to create a validation rule on creation, so I might use this feature more now.

I’ll second this!

1 Like

5 Likes

We will add it soon

1 Like

Will it be possible to extend this to Spaces and Entities ?

User mode → See only Spaces and Entities I have access

Architect mode → See all Spaces and Entities

2 Likes

Not sure anybody is up for a response here, but I just wanted to sanity check my understanding of this point: In this example are we assuming that the db in question here would have some name of its entities that is the same as the db, so say “work items.” So the db would be named “work items” and consequently so are all the entities in that db. If there are 2 “types” as mentioned here, that would have to be a tag of some sort - so Work Item of type “Project” and work item of type “service call.” And the multi-view feature here allows for a different view depending on the tag - which could be a single-select field.

I definitely have examples of this in my instance, one would be “story” as a db for dev work, and two types we have used are “user” and “technical,” so in this case I could use a different view depending on the type of story…

One reason I wanted to check here is once upon a time databases were actually called “types” so this terminology had me thinking too.

Thanks!

1 Like

Your understanding is correct :slight_smile:

1 Like

Thank you appreciate you getting back on this!

Added in latest release