January 8, 2026 / 🧞‍♂️ Custom Database access, Duplicate automations to other databases

News & Announcements Changelog
1

Happy New Year, everyone! Here is the modest first release of 2026.

:man_genie: Custom Database access

Introduced a few weeks ago, this functionality is no longer experimental :hatching_chick:

Quick recap: if the default set of Database access templates doesn’t cover your use case, you can now define your own custom template. For example, to allow users to edit but not delete any Task:

image
image2232×1732 194 KB

Since the minimalistic experimental release, we’ve added a few touches to the template management:

  • Reorder the templates via drag’n’drop.
  • Conveniently switch a template’s availability from all to selected Databases — or hide it altogether.
  • See all the people who have access via a certain template.
  • Get a heads-up when trying to update capabilities for a template that is in use.

The template management screen has also seen some designer’s love and is not hidden in settings anymore:

image
image3208×1920 323 KB

Check out our updated user guide for more details.

:clinking_beer_mugs: Duplicate automations to other databases

Now you can duplicate automation rules and buttons to other databases. It can be time saving when you have similar databases and want to have similar rules as well.

Note that this action works with the “best effort”. For example, if there is a field missing in the destination database, it will be marked as Deleted Field in the duplicated rule, etc. Find Duplicate to action in … menu for a rule or button and try it out.

image
image2708×1780 367 KB

:butterfly: Improvements

  • UI:
    • We refreshed collection fields on the Entity View to match the new Files collection — now everything looks consistent (and good!).
    • Action buttons are grouped into a single item in context menu if there are more than 3 of them.
    • Help & Support menu got some update. Added links to mobile apps, removed link to X, etc.
  • AI: AI Agent answers basic questions faster now.
  • Linear Integration: Delta sync implemented for Linear, so now it should sync data faster.

:shrimp: Fixed Bugs

  • Inbox: Fixed inconsistent behavior in Inbox for deleted entity.
  • Notifications. Fixed a case when Slack notification setting is not updated on UI after I connect Slack account.
  • CSV import: Fixed field value in fields list if name is generated via formula.
  • Desktop: Ctrl+zoom shortcut works on Windows now.
  • Required fields: Fixed a case when Cmd+enter does not submit new entity after selecting required date/creating a new related entity.
  • Forms: Fixed a problem when files uploaded via Form into single-file-field stay marked as temporary
  • Stability: Fixed an error when deleting related database while being on database screen
  • Mobile:
    • Fixed a case when address field in public forms is not editable on mobile devices
    • Now you can open entity card on the whiteboard
10 Likes
Zoom / Presenter Mode in desktop app
[DONE] Copy existing rules
[FIXED] Right-click menu longer than browser window
3

Great start to the year! Looking forward to using the database access.
Duplicate automations is FANTASTIC!

4 Likes
4

Happy new year!

Notes about database access templates:

  1. I love this feature so much. Thanks for building it!
  2. When setting a template to “No Databases”, those were already granted this template still have access with the disabled template.
  3. Wondering if there’s a way to make “Space Access Templates” as well. Not sure about the need, but might be useful. This would maybe allow a template for “View Architect + Data Editor”…?
  4. I’m a bit more confused about this positioning in terms of settings placement. This is a workspace wide setting (from my understanding), but is hidden inside database access. What I edit here, is by default shown on all databases, and it also shows all other templates, even the ones not relevant to the database i opened it from. There’s the database indicator showing which ones are from the one I opened and which one not. But in my mind if these are global settings, it makes sense to be in the setting page. I think. Or make the database access templates per space (like how entity access is defined per database), then put in the space settings. Not sure about best way, but I think it’s a bit confusing at the moment to new architects.

Cool new automation duplication! Showing the name of the broken field would be helpful for relinking.

Like the new design of the collections. Looking forward to the new branding in general!!

Also I noticed a new dot indicator when filters and sort are on. Neat!

3 Likes
5

Thanks!

Yes, this is by design:

Making a template unavailable for a certain Database doesn’t revoke existing access, it only prevents sharers from using the template in the future.

The Space level is trickier, since ideally you’d want to specify not only access to the Space itself but to each Database of the Space — similar to how you extend access via relations on the Entity level. Maybe we’ll get there, but it’s unlikely in the next year. As usual, depends on the demand — so far we haven’t seen much.

We started with the settings page, but it just doesn’t deserve such prominence. Custom Database access templates are quite a niche and rarely used feature, and we didn’t want to introduce extra complexity to the settings because of it.

We’ll see if the architects get confused.

2 Likes
6

Thanks for the reply!

Huh! The more you know! Just learned that this is the same for entity access. Some popup here might be nice, maybe a question of “Convert everyone from this template to another?” Maybe?

True! Ideally this is the case and would be great. But if it started with the same access across all databases in the space (as space access currently works) + control over views access. That would already by quite nice. It would then replace the “Share without extending” with custom access.

I’m wondering where the User database permissions will be. Maybe there can be a “Permissions” tab in workspace settings? Not sure.
But yeah, indeed it’s probably a niche feature. Just thinking about where it makes most sense from a “What does this really do” perspective. Making the feature more centered around creating templates for single databases then the option to “Share Globally” or “Make available to other databases”, then it would make more sense to be in database access settings. Its a small thing, but could make a bit more sense with the placement. Not 100% sure though.

Edit:
Note that I think ideally it works the same as Entity level access templates. Set on the space level, then avaliable to all databases in the space.

7

Love the updates guys, will try them soon!

One thing I didn’t particularly like was the border around the entity views. I understand the intention is probably to make it clear which content belongs to which entity, especially when we have multiple entity views on screen.

I remember we previously had a background color approach without borders – that was interesting. Then later we had neither borders nor backgrounds. Now we have borders.

I think the background solution worked well. Alternatively, borders could work too, but perhaps not such a strong border. A more subtle border (like 0.5px or 1px with reduced opacity) might be better. I made a quick experiment in the inspector to test this.

1 Like
8

Thanks for your feedback! This is specifically related to dark theme: borders are lighter there, while background color has a darker shade, creating a look that it’s only border without background. We’re working on improving it in some future

2 Likes
9

I see what you mean. Switched to light mode and its looking way better than the dark theme.

Hope the dark theme gets some polishing as well.

Thanks

1 Like