# "second brain for teams" **URL:** \ **Category:** Ideas & Features\ **Created:** [July 20, 2021, 12:38pm UTC](https://community.fibery.io/t/second-brain-for-teams/1822 "2021-07-20T12:38:16Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![cover](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cover/32/11891_2.png) [@cover](https://community.fibery.io/u/cover)\ **Post date:** [July 20, 2021, 12:38pm UTC](https://community.fibery.io/t/second-brain-for-teams/1822/1 "2021-07-20T12:38:16Z")
# Sorry if it’s wrong place/category for such topic. Hi, I’ve just read [#34. Thinking about the Next Big Thing in Fibery in June 2021](https://fibery.io/blog/chronicles-34/) and was stroke by “Feature-wise it will lead to Entity View / Documents re-design with Blocks” as this is something I’ve been thinking about daily for 1 month now working inside Fibery. I will try to draft my problems and ideas below. ATS & HRM. 1. I’d like to literally build Person (Candidate and Employee) page using data from Model (Types). It’s very limiting to have all fields and 1-1 relations in the right column using 25% of page space and other fileds and n-n relations for the rest of 75% of page. 2. For each Person I’d like to attach Skill Matrix which is naturally a Table but for now I can only manually build Table inside RichText area or display list of Skills+Levels as a one-level list inside n-n relations block. So what I see as a solution is to embed Table View of SkillMatrix Type filtered by Person…or ideally is to introduce [key, value] array as System Field. Sorry for my ignorant language, just trying to explain and illustrate my UX. 3. Almost the same story with TechStack and Domain Areas expertise…generally what I try to do is to reflect CV/Resume data and actualise it in Fibery. 4. Quite often I use only “Lookup field” and want to hide Relation from Entity view. 5. Back to Employee page/profile I’d like to have list of one-on-one embedded and collapsible/expandable for each item. 6. Further, in future, I foresee the need of structuring one-on-one and other surveying/interviewing activities with Question and Answer Types and would love to see their Views embedded into Employee or Document Type. CRM 1. Rate Card. Inside HRM app for each Person I have a Rate Card which consist of number of Fields and alltogether addition in “Prime Cost” Field. Now in CRM app I want just +1 Field “Markup” for each Person and Account combination so to get Rate Card for particular Customer. And again I want to see this as Table View inside Customer or Project Type. I didn’t yet researched this well and perhaps I can implement such encapsulation through Formulas/Lookup Fields but my idea is to have sort of System composite Type which incorporates another Type. ---
**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:** [July 20, 2021, 12:52pm UTC](https://community.fibery.io/t/second-brain-for-teams/1822/2 "2021-07-20T12:52:15Z")
Thank you for the cases! From my understanding, 1-5 will be possible, it just matches our ideas. 6 is interesting, we should dig deeper here. I don’t get CRM case, unfortunately… can you try to explain in differently? ---
**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:** [July 21, 2021, 12:21am UTC](https://community.fibery.io/t/second-brain-for-teams/1822/3 "2021-07-21T00:21:55Z")
There are a bunch of existing feature requests (as well as officially expressed plans from the Fibery team) which I think will likely meet most or all of your needs. - [Embed Custom Views into Entity View](https://community.fibery.io/t/embed-custom-views-into-entity-view/936) - [Individual Layouts for a node, hide fields etc](https://community.fibery.io/t/individual-layouts-for-a-node-hide-fields-etc/995) - [Polymorphic relations. When creating relation, ability to have entire App from which to choose, and not just Type](https://community.fibery.io/t/polymorphic-relations-when-creating-relation-ability-to-have-entire-app-from-which-to-choose-and-not-just-type/425) Etc. Your specific use cases are no doubt useful in defining exactly how all these related features and functions will work! ---
**Author:** ![cover](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cover/32/11891_2.png) [@cover](https://community.fibery.io/u/cover)\ **Post date:** [January 13, 2022, 11:26am UTC](https://community.fibery.io/t/second-brain-for-teams/1822/4 "2022-01-13T11:26:55Z")
Hi, long time no reply from me but now I’m here and eager to explain/simplify my HRM-CRM case. HRM-\>Employee: - Rate, $/h the Person get on hands - Prime Cost, $/h is a formula based on Rate + some variables and lookups in “Salary Review” CRM-\>Account-\>Project: - ExternalRate for particular Person, $/h is a formula based on Prime Cost (from HRM space) + some variables So basically I want to: - see the list of Persons for each Project with Rate, Prime Cost, External Rate - see the list of Projects for each Person with Rate, Prime Cost, External Rate This is what I hope will be possible in some future along with major releases of “second brain for teams” initiative. True or false? 🙂 Thanks!