I realized that you cannot create a page and share it with only one other person today. This upends my usual strategy of having a dashboard for 1:1 conversations with employees.
Assuming that a page is an entity in a ‘page’ db, then you can definitely jsut share it with a single person. Make sure the database that the entity is in is not shared with anyone, and make sure the space that the database is in is not shared with anyone.
Then open the entity and use the Share option:
How secure do you need these to be? Is it a problem if the rest of the users can see the “Check-ins” even if they are not their’s?
If so, doing this in Fibery would be a problem…
If not, I would create a new database called “Review” or “Performance Review” where you can auto share with the people tagged. The rich text is secure, but if you have single selects or relations like you have in the checkins, those are not really secure from others in the workspace.
If the performance review is just a RTF with embedded views, I’d go the approach of having a “Documents” database, and different document types that serve as templates. Based on the template (auto copy fields from type when linked), it either shares it with the team (auto access) and everyone has access, or shares it just with the person who triggers, so that then they can share with someone else (private doc).
But I’m also not exactly sure about the use case. The screen shot you shared is just one doc. Are the check ins part of the review?
They’re a pretty popular strategy for team management and a usecase worth refining.
I don’t think pages-as-dashboards are a complete concept without the ability to share them with a subset of people. And creating one space per employer-manager relationship does not scale. I think creating a database where each entity is shared with one employee and their manager may be the only option as of today.
I was kinda joking - we do have 1:1 meetings internally (but we don’t call them performance check-ins, and we don’t put much emphasis on creating a shared record). It’s definitely a valid use case.
I’m tacking another swing at this today. I intended to use a formula to get tasks in a a list. However, I cannot seem to control the order that the tasks appear. Shouldn’t this formula return task entities in chronological order?
Should do! I just tested it too and you’re right, it just sorts them by rank… very weird.
I think the sort function is mainly to be used with the First or Last function, as opposed to setting ui. You can’t set custom sort or filters on lookup fields (with ui) so I assume they just default to sort by rank without respecting the formula sort.
I think it’s a bug/issue.
Workaround would be to add a relation. Then either auto-link or just use the window to show context filtered tasks (from the person relation. But you would need to change the relation type to to-many because context filters only work with that at the moment i think… or just auto-link…) Then you can filter and sort by UI. And you have more control of the views.
This is it.
Formulas basically work on the backend and then the UI settings determine the sort order.
It’s not a bug - it’s how it is designed to work.
Of course, I can imagine having the ability to set the UI sort order for collections that are created with a formula (or lookup) would be nice, but that’s a different story.