# Grouping of Apps and Entities \[DONE\]

**URL:** <https://community.fibery.io/t/grouping-of-apps-and-entities-done/521>\
**Category:** Ideas & Features\
**Tags:** left-menu\
**Created:** [January 15, 2020, 7:48pm UTC](https://community.fibery.io/t/grouping-of-apps-and-entities-done/521 "2020-01-15T19:48:49Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [January 15, 2020, 7:48pm UTC](https://community.fibery.io/t/grouping-of-apps-and-entities-done/521/1 "2020-01-15T19:48:49Z")

</div>

Hi guys,

I have had a few situations when building out my Fibery where I wanted to see some groupings in my Apps and entities.

Here are a few examples:

I have some apps for functions across my team, like Marketing, Sales, HR, and others that represent tangible items - assets (computers, etc), Vendors, Customers. I treat these types of entities internally similarly. It would be great if I could group the apps along these lines. Otherwise I was thinking about creating a new app with just the two groups and linking, but that seems like a lot of extra structure I really shouldn’t need

Within Apps I can see this need even more. I have a few types of Vendors I distinguish - Suppliers of stuff like office supplies, phone services, etc. that are not part of my business operations, and then vendors who I work with closely for services integral to my business, like ad campaigns, licensing, etc. They are two different types of Vendors, which I have in an app called “Counterparties” which I also use for Customers. I was thinking should I create a type “Vendor,” then two sub-types “Business Driver Vendors” and “Suppliers?” That seems like overkill, and it occurs to me if I could simply group these Vendors, it would be a simpler set up. Without the extra type to distinguish the two right now, I’m not sure how else to represent these in Fibery. And I don’t want to create the extra App called simply “Vendors” with just two types, either.

Actually, sorry I’m going to edit this because as I think this through, I’m trying to figure out in fact how do you represent a hierarchy in an app? It seems it doesn’t make sense to use the concept of “levels” over 2 deep, as then you get a mid-level that is nothing more than a grouping of real types that have actual entities in them. Am I understanding this correctly? And if so, is there any suggestion on how to handle this right now?

Thanks!

---

<div class="post-metadata">

**Author:** ![dathat](https://avatars.discourse-cdn.com/v4/letter/d/b77776/32.png) [@dathat](https://community.fibery.io/u/dathat)\
**Post date:** [November 9, 2021, 4:16am UTC](https://community.fibery.io/t/grouping-of-apps-and-entities-done/521/2 "2021-11-09T04:16:52Z")

</div>

More than new templates, I would love to see new UI/X powers.

- Pull together docs that have embeds of charts, editable entity tables, etc.
- Easily group “app” pages in workflows for different uses.
  - GIST Idea entry \> Customer discovery OR Competition Research entry AND [finish both to some metric before next] \> Product entry

Etc.

On the left nav, it would be cool to be able to just group the apps for easier viewing, too. They can really pile up! 🙂

---

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [November 9, 2021, 4:12pm UTC](https://community.fibery.io/t/grouping-of-apps-and-entities-done/521/3 "2021-11-09T16:12:43Z")

</div>

> [@dathat](#):
>
> - Pull together docs that have embeds of charts, editable entity tables, etc.
> - Easily group “app” pages in workflows for different uses.
> - GIST Idea entry \> Customer discovery OR Competition Research entry AND [finish both to some metric before next] \> Product entry

I’m not certain that what you describe is actually what the original request that your topic was merged into is about: “Grouping of Apps and Entities”.

That said, how I read your suggestion is something more like this:

> **[Beau: automate client-facing workflows](https://beau.to/)**
>
> Build, visualize, automate your client-facing processes. All with one, easy-to-use solution.

Or

> **[Process Street | Checklist, Workflow and SOP Software](https://www.process.st/)**
>
> Checklist and workflow software for businesses. Create recurring processes and standard operating procedures in seconds. Get started free.

And if that’s the case, then yes, I think that would be a really cool capability to arise out of the Blocks functionality! And it seems just possible that it might (or could). So if my read of your request is correct (setting aside that you end with being able to group apps in left nav), then perhaps this needs to be its own topic.

---

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [December 17, 2021, 4:02am UTC](https://community.fibery.io/t/grouping-of-apps-and-entities-done/521/4 "2021-12-17T04:02:51Z")

</div>

> [@dathat](#):
>
> On the left nav, it would be cool to be able to just group the apps for easier viewing, too. They can really pile up! 🙂

This seems like in spirit is related to my original request. Perhaps with some sort of Smart Folders - but Folders that would also exist as “full class citizens” so collect references, be accessible via # mention, etc.

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [December 19, 2021, 6:36am UTC](https://community.fibery.io/t/grouping-of-apps-and-entities-done/521/5 "2021-12-19T06:36:57Z")

</div>

3 posts were merged into an existing topic: [Workflow Extension Enhancements for Advanced Dev Teams](https://community.fibery.io/t/workflow-extension-enhancements-for-advanced-dev-teams/1266/4)

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [October 4, 2024, 6:40am UTC](https://community.fibery.io/t/grouping-of-apps-and-entities-done/521/6 "2024-10-04T06:40:33Z")

</div>

See smart sections

> [@May 9, 2024 / Smart Sections and 15 quality-of-life updates](https://community.fibery.io/t/may-9-2024-smart-sections-and-15-quality-of-life-updates/6166):
>
> We skipped last Thursday (holidays), so you are getting the double dose of updates today! gift giftSmart Sections (experimental) [turn-smart-folder-into-smart-section] Most companies are organized both functionally (design, development, sales, etc.) and cross-functionally (by product, client, or cross-functional team). However, when you pick a collaboration tool, you are typically forced to build your workspace around one organization and sacrifice the other. Fibery was no exception: acc…

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [October 4, 2024, 6:41am UTC](https://community.fibery.io/t/grouping-of-apps-and-entities-done/521/7 "2024-10-04T06:41:06Z")

</div>


