![]() ![]() ![]() Then hit the delete key on your keyboard to clear the selected cells.Select the cell you wish to delete by clicking and dragging to select multiple cells or holding the shift key while clicking/using the arrow keys.From the view switcher, select the view you wish to lock.With creator/owner rights to create a Locked view, do the following: ![]() ![]() The steps are very similar to creating a personal view. Other collaborators will still have the ability to view or make changes to the information with the records. It’s useful for preventing any unexpected changes to a view’s set up which could potentially disrupt workflow. The Locked view feature is also available on the Pro and Enterprise plans. From the view mode menu, choose the view mode you want for the current view.Next to the view’s name, click on the View mode button.Steps on how to create a new view are shown in the Additional FAQs section of this article. You could also create a new view to make personal. From the view switcher, select the view you wish to make personal.Click on the Views option found towards the top left-hand corner.I have this need in Task Management I am running in Fibery, where I have groups of Tasks in Types that I’d like to have only certain users see, and not the whole App’s worth of Types. The addition of the Type-level permission makes it easier to break down groups of Entities within an App. Via mentioning a user, they get access to an individual Entity only. You can access particular users to a Type, much as you do now with a whole App So in the case of Fibery, I think you have a great chance with your existing hierarchy to do a similar approach that would be very familiar to those coming in from these tools - and perhaps others who handle things similarly like Hive, Monday, Teamwork Projects, etc. You can “share” lists/folders/projects to a particular group. If you a user within a comment stream, they get added just to that particular task One of my favorite, which is central in Wrike, and Asana, and ClickUp - who I might loosely consider a similar “triumvirate” of “Task Managers” like Airtable/Coda/Notion is within the “nocode” sub-space, all do this: Many of the tools I’ve used have nice ways to handle these levels of permissions. So stuff like development chores, recruiting tasks, recurring posting of blog articles each week, etc. I am trying to set up all all “work items” in my team (small software development with some marketing, HR, content, etc.) can be tracked in one place. Here is my situation and why this would be useful: I know this is something you are thinking about, but I wanted to add the request here as a sort of “upvote” to make a case to prioritize this. Hopefully, these sensible defaults will work for most scenarios: To share a Project and all its Tasks (and their Subtasks), we need some kind of inheritance.įibery knows better than vertical hierarchy distinguishing between one/many - one/many relations and making things difficult for permissions. Those with Full Access are free to share an Entity with an individual User or a Group by picking one of these levels.Īll Entity “companions” are shared automatically with the same level: Files, Documents, Whiteboards, etc. There are 4 default levels of access (the same is in Notion, what a coincidence): Hopefully, we think we have a decent model. Well, they are extremely hard to get right - even conceptually, without thinking about UI and implementation. You might ask: if they are so important, why the fu Entity-level permissions haven’t been implemented yet? Solving climate changeĭelegating tasks to contractors, splitting CRM among sales folks - the list goes on…Īlso, based on how Fibery works under the hood, we need some form of Entity-level permissions to build My Space, Read-only users, and collaborative external sharing. Sharing everything inside a Product, Objective, or Initiative would facilitate cross-functional collaboration™ (buy our book on successful enterprise success®). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |