April 24, 2025 / Access templates explained, full/compact Forms, callouts in markdown

We’ll walk you through all of these updates in our product webinar next Wednesday. Register and join us live.

:exploding_head: Access templates explained

Access templates are a unique and not necessarily self-explanatory Fibery concept. Once you realise you can share not just individual, say, Projects but also their Tasks, Meetings, and those Meetings’ Action Items, you are empowered! The problem is, “once” can also be “if”.

Guides and tutorials are nice, but we believe unique concepts deserve in-product explanations:

Now, we explain what an access template is before you create one. Then, we clearly indicate there are two steps to the process: configure a template and then use it for sharing. Moreover, you can enable automatic sharing or share a specific entity without leaving the page.

Certainly, these changes won’t make access templates as simple as 2+2, but we hope we are moving away from ∛(π²)×ℯ. If you’ve been postponing trying access templates, now is the time. Let us know how it goes.

:locomotive: Draw a straight line on Whiteboard using Shift modifier key

To draw a straight line, hold down the Shift key to constrain the line to horizontal or vertical. You can also select an object and click a blue dot to draw a line, and holding Shift will make it straight.

:first_quarter_moon: Full/compact form setting for Quick Add forms

Now you can define a form layout for New buttons for any View. Compact Form is not displaying fields descriptions and it is more dense. Full form shows all the details and it more sparse. Choose desired layout for every form on every view.

:information_source: Write callouts using markdown

Now callout blocks are properly included when you import or export rich text via markdown: in automations and API or when copy-pasting between (some) tools.

Unfortunately, there is no industry-wide standard, so we had to come up with our own syntax that would support icons and colors:

> [//]: # (callout;icon-type=icon;icon=exclamation-circle;color=#4a4a4a)
> first line
> second line
> third line

Try it in your automation markdown templates!

:butterfly: One-liner improvements

  • Timeline view: now you can collapse/expand groups.
  • Context views: if there is a Field needed to be filled when creating an entity on a Context View, it mimics the required Field design.
  • URL Field: when displaying URLs, we trim https:// and www now so that you can see more of the actual link.
  • Sign-up: when you create a new Fibery workspace, we try to set the workspace logo based on your email domain.
  • Website: our website content is easier for an LLM to scrape now. GEO FTW!

:shrimp: Fixed Bugs

  • Database permissions: DB-level Creator doesn’t have access to the DB settings screen.
  • Inbox: Inbox is missed sometimes on 1st opening workspace after installing from ‘No code’ template
  • Performance: Grid memory leak → Update AG Grid to latest version
  • Fields:
    • Hovering over a link shows a tooltip, and the link exceeds the box
    • Number field became read-only if convert it from money to percent in some case
    • z-index issue with location field in quick add pop-up
  • Google Calendar integration: is should be auto-create Calendar views for personal integrations
  • Calendar view: Calendar week, day mode: new entity placeholder disappears in attempt to select date/enum/relation value for formula field
  • Forms:
    • Keyboard for required fields and formula fields popover should be unified with Quick Add
    • Increase the bottom spacing in the Form View
16 Likes

Love this!! But i wasn’t able to find how to do it… Is it still hidden or is there a guide that shows?

Also a (very subtle but noticeable) change to the table view is that -webkit-font-smoothing is different now to other views. Making the font a bit thinner than normal.

Here’s the way:

3 Likes

Thanks! Would it be possible to put it in the popup itself? Maybe under “Fields”? Like this it’s not possible to change the layout of the “Default” form. (not the one set to default, the one that is when there is no form :sweat_smile:)

These quality of life updates warm my hear. I’ve very much appreciated the improvements to form views.
Thank you for the markdown callouts! Can’t wait to add them to my workspace :sparkling_heart:

1 Like

Solid update, thanks! :slightly_smiling_face:

This is one of the drawbacks of building on markdown. Syntax as a comment hack is not great. A format with a good extension API such as that in AsciiDoc would be lovely. Kramdown is a markdown variant with strict syntax and definite rules, which also includes a documented extension mechanism. These still aren’t industry-wide standards, but do help to make any extensions consistent, predictable, and composable, and open the door to drawing on existing ecosystems of extensions.

This is most probably due to new ag-grid version we are using for tables. We are still tweaking details

2 Likes

But not the User Guide.
Grok:
I was unable to access or scrape the specific Fibery User Guide page at Fibery (https://the.fibery.io/@public/User_Guide/Guide/File-API-265) due to restrictions or limitations in accessing the content, which may be related to authentication requirements, paywalls, or the page being unavailable at the time of the query on April 26, 2025.

1 Like

There are many things I love about Fibery. However, putting the documentation in published Fibery pages simply shows off many of the ways that Fibery is not ready for this use case. The guide is generally not indexable. I think we’re going to need a publishing app on top of the native databases similar to how the reports sit on top of the data.

What do you mean by this? What would you like that is not currently possible?

Here are the main areas where the experience feels limited:

A. Nested Navigation Is Hard To Work With Once Inside Articles

The guide structure is heavily nested, but it’s not easy to see where you are in the hierarchy at a glance. There’s no full, persistent sidebar or expanded table of contents showing the overall map of pages, subpages, and internal headers. As a result, it’s difficult to quickly jump between related sections without retracing steps or guessing where things live.

B. Inefficient Search

I often resort to using Google search rather than the Fibery site search to find specific topics. Similar concepts (e.g., Markdown templates) are mentioned across multiple articles but with varying depth or specificity. Because human-inserted links between related pages are inconsistent, search and navigation feel fragmented.

When two panel pages are open, I have to use the browser based search as a better way of confirming what I’m looking for is not on the page.

Now that both APIs are included in the guide it’s even harder to find the exact information you need about a specific implementation for the API/scripting context you’re looking for. Some of the issues in this section does come back to the content itself, but it has made searching and finding what one needs painful.

C. Two-Panel Navigation Creates Friction

The two-panel layout (navigation on the left, article on the right) can sometimes present an obstacle to seeing related articles side-by-side. When working from a starter page that lists additional pages to review, clicking on a second article replaces the current one, which disrupts comparison and deeper learning workflows.

Overall, the guide lacks the effectiveness of simple wiki websites. While content exists, it’s not easily searchable, cross-referenced, or navigable for deeper technical use.

4 Likes

Thank you for the links. However, why do you think that the comment hack is not great? The main reason we choose comments is because they are backward compatible with most modern markdown parsers. You can always retrieve the document in JSON format and easily convert it to the desired format.

1 Like

Looking forward to this fix :slight_smile:

Published Fibery spaces should be indexable by search engines. We see it on our own published guides.

1 Like

This is true and an often easier way to find what you’re looking for.

You are right. There was a problem with how LLMs treated @ in the public pages URLs, replacing it with %40, triggering unnecessary authentication.

We’ve made a tweak on our side. Please try scraping again now.

1 Like

Thank you, Grok and ChatGPT can now access it. Some feedback from them:

"For optimizing it more for AI assessment:

  1. Adding Schema.org markup (e.g., TechArticle or APIReference) to provide explicit context.
  2. Including tags for description and keywords to improve discoverability.
  3. Specifying language classes for code blocks (e.g., language-graphql) to aid parsing."
2 Likes

Just tried with Grok, not working…