Would still love to see this, quite a few votes so hoping for some movement, especially now that Notion has it. Would really help cut down on the proliferation of drop downs and fields in Entities, which is something that plagues my instance.
Thanks!
Hi, conditional fields can be split in 3 requirements:
Can we have at least the second one in the following weeks? This is something Coda provides extensively (conditions can be expressed with a formula), Notion just in forms, and it is fundamental for usability in many-fields per item scenarios and when button should not be pressed in specific conditions.
Thanks a lot
Giuse
I hope this is mostly covered by relation filters, no?
Fields themselves don’t generally have formats (font style/colour, background colour, etc.) with the exception of select fields having bg colours, so having formatting dependent on another field value is a long way away.
If you mean that the presentation of a field in an aggregated view (table, board, etc.) then some views do include colour-coding by field values, but the formatting applies to the whole record.
It will certainly not happen in the following weeks, maybe (but not certainly) within the following months.
Hi Chris and thanks for your reply.
You are right that 1) is mostly covered by relation filters (with some exception like relating entities with search).
About 2) and 3) yes, I mean being able to add a format to every field (like a formula that sets a CSS class for each field). For buttons is particularly important, so if not weeks but in a few months, I will wait 
Thanks again
Giuse
I fear I have given a false impression - I think it is unlikely to happen in the next few months. It might be many months (or even quarters) before it happens, sorry.
Hey Fibery team and community,
Would love to see a native feature that allows conditional visibility for fields, based on status, user role, or any other property. For example, hiding an “Internal Notes” field unless the user is part of the “Managers” group—or only showing the “QA Checklist” when the status is “Ready for Review.”
I’ve been using some creative workarounds with formulas and views, but true conditional logic for field visibility would really level up app UX, especially for larger teams with different permissions.
Curious if this is on the roadmap or if others would find this useful too?
Cheers,
Jhonn Mick
Hey! Welcome to the community!
Wondering if this is more in the perspective of permissioning and access, or UI/UX.
If it’s just for UI, you’d be happy to know that it’s coming! Fibery
It’s specificslly for entity view, and not for all views. Not sure if you had table view or something else in mind.
If it’s field level permissions, that’s something the team has said a few times that isn’t coming any time soon.
See here for more details: Field-level permissions
If the permissions are already in place that Internal Notes are not vislbe to non-managers, then the Internal Notes field will show empty for them, and you could use the FiberFlow extension to hide empty fields. It will be hidden if empty for everyone though.
I think that FiberFlow will likely cover conditional hiding based on field @derbenoo ?
Is this request basically the same as this or is it about field-level permissions?
(composed this before seeing previous replies!)
@ChrisG This link leads to a page with a frame that seems to require a Figma account. See below.
Is there a way to present this info without a user requiring to have a Figma account?
Thanks
It’s not possible.
The roadmap item description is based on the internal feature spec, which includes Figma mockups.
In this case, the Figma mockup contains the following:
Thank you for the screenshot @ChrisG
Interesting choice. I’m seriously trying to limit the amount of accounts / apps for both personal and office purposes - free or not.
PS: I know this multifunctional database app with an amazing whiteboard view for exactly this kind of diagram… Full disclosure, if you use my link to sign up I get a kickback - yet I would highly recommend checking out Fibery.io (thank me later)
Thanks so much, everyone, for jumping in and sharing your thoughts!
@ChrisG, really appreciate the clarity on the Figma setup and for posting the screenshots. Super helpful.
@Hendrik, totally hear you on the account overload… it’s a real thing. Also, thanks for the Fibery shoutout, love seeing people share tools they genuinely find useful.
Excited to see conditional visibility coming, it’s going to make a big difference for how we work with the UI!
100% Fibery Team PLEASE implement this, as well as the concept of Field Sections, allowing a group of fields to be conditionally activated. Otherwise it’s always compromise territory balancing number of fields with navigation ease.
Maybe I’m missing something obvious somewhere, but is setting Entity View based on field value going to be the way of implementing conditional field visibility?
I guess my questions is will any conditional field visibility always create a new entity view? Like I may just want to have a field hidden based on value in another field, but I don’t necessarily want to treat that as a brand new entity view.
@ChrisG am I interpreting upcoming conditional entity view correctly?
The feature that @RonMakesSystems pointed to is not quite the same thing as ‘conditional field visibility’. It is conditional view selection.
It might address some needs that people have, but I wouldn’t consider it as ‘the solution’
Got it - that was my hunch. Then it seems like this request could then safely be merged into Conditional fields in apps, yes?
Some alleviation of this problem was released today
