Well, this thing looks and feels like a solid information system that can only be replaced by an internal website. It unites project management and a knowledge base. I love Notion, the only things that keep it from becoming huge are the lack of public API and the inability to have a local Notion server for the enterprises to use.
Quick question: at 5:05 you talk about using a formula within the projects database to calculate percentage complete from the tasks database. Have you got a video or a description about how that is best done? Thanks in advance.
Thank you for recording this video. I thought I had it down when I participated in your recent crowdcast. However, after watching this video I realized I made my setup way to complicated. Now, I know what I need to do to simplify my system so that it can work for my needs.
Great video William. Appreciate you helping out the Notion community like this. Quick question if I may. Following a similar setup to the one you outlined but using the example of being a furniture maker . Typically one would have a number of projects on the go, each with a large number of tasks associated with them. What I’m looking for is a very efficient way to input a number of tasks, typically as they come to mind, and then be able to efficiently order them in the correct sequential order. As the project moves from the initial planning phase through to the actual making/implementation phase many more tasks will spring to mind that need inputting into the correct sequential position. Finally when the project is completed one would end up with a complete “schedule of works” if the project was ever repeated. I wondered whether you’d made any videos that touched on this kind of thing, really focusing on quick task entry and having a step by step sequential schedule of tasks. Many thanks again
Thanks for the kind words, Mark. Where these tasks lists will resemble one another from project to project, I definitely recommend creating templates as much as possible: www.notion.so/Database-templates-454ed5ab5bd24226b58d176697bd7e10 For these templates, you can have "placeholder" tasks that you can quickly duplicate, then "relate" to the new project. For one-off projects with unique collections of tasks, the fastest way to add tasks is through a Table view. You can type the task as the last item in the table, then hitting Return/Enter will automatically create a new item for rapid entry. Of course, for both of the above options, you're using a view of the master Tasks database. If that's too complicated for you, you could avoid the master Tasks database and instead use an independent Tasks database for each project template. That will allow you have the tasks prepopulated without having to duplicate and "relate" them. So recapping, three approaches: 1. Create templates wherever possible, where "placeholder" tasks exist within the "view" of the master Tasks database. Each time you use the template, you'll duplicate the "placeholders" and "relate" them to the new project. 2. Rapidly enter new tasks within the filtered Table "view" of the master tasks database. 3. Forgo the master Tasks database and instead have an independent Tasks database for each project, which will allow you to prepopulate all tasks (without duplication).
thanks for this video really helpful with my agency workspace setup i have seen many videos yours is the simplest so far but how can we manage things like giving the access for some table and for some team members i dont wanna share my whole workspace with them so can you show how can we do that for all departments in details please
Thank you. You can selectively restrict access to any database item. If you'll have many private items, I recommend creating private versions of databases-either for yourself or per Teamspace.
Hi there! I love your videos. I just discovered notion and my nerdy self has fallen in love with it. I was hoping of you could help me with something though. I want to make a project database template that will automatically show a view of my resources that have the same Area as the new Project. Is there a way to link the projects and resources through a similar property like the relation to the Area? I'm thinking maybe I would need to have a different project template for each area and just have a filter on the resources database view filtered by that specific area.
Thanks so much. The template can only filter for itself. In other words, you can only filter Resources related to the new project. Your choice are to: 1. manually adjust the filter after implementing the template for each new project; or 2. use a tool like Zapier or Make to relate the new project to all resources related to the project's area. Sounds like you'd make a great candidate for Notion A-to-Z. 😃premier.notion.vip/a-to-z
Under Contacts>Clients>Client1, I'd like to create a tasks completion table where the data comes from the master database, and filtered by client name. Then I'd like to share that particular page with client1. Client1 should be able to change the status of the task, add comments, etc from that page, but must not be able to see data of other clients, nor even any other pages. ***How can I achieve that without sharing the entire master database with all the clients?*** Spent 2 days figuring this out with no luck.
Thank you. Notion does not currently support sharing by filtered view, so you'll need to share tasks one-by-one or create a private Tasks database for the client.
Thanks David. You could use a Relation property to link People with Resources. Sounds like you'd make a great candidate for A-to-Z: premier.notion.vip/a-to-z
Thank you. You can apply Teamspaces to the Bulletproofing Method in a few ways. The most common is to create "micro" Bulletproof Workspaces-each with its own master databases-for content that should be visable only to certain groups.
@@edvinbjork1481 Bulletproof is evolving within Notion A-to-Z, which will offer a variety of resources related to Teamspaces, including tutorials for incorporating them into the Bulletproof system, with functional demos. premier.notion.vip/a-to-z
Hi Will! Love this. Implementing notion within my team @HIVED. I had a question, where do you see tasks going for things that are continuous? that don't have a defined start and end. e.g. Customer questions that need to be answered. or day to day operations / fire fighting urgent issues. A distinct 'project' with a start and end doesn't seem to fit these kinds of tasks. But then, just putting them as a task without a project seems disorganised. I hope that makes sense. My sense is to create 'ongoing projects' that have multiple tasks attached.
Thanks Jack. Bingo - under this version of Bulletproof, the best approach is to create ongoing Projects for these circumstances. For your customer inquiries examples, however, you might consider and independent database for tracking those tickets. Also - in newer implementations of Bulletproof, Tasks can be related directly to Spaces (formerly “Buckets”) or Organizations.
Great video William, would you mind if you can share the workspace with us? Curious about the Resource table/page. How can you maintain different types of resources in the same table? Thanks
Thanks Michele. You can access the Data page here: www.notion.so/loggerheadlabs/Data-20d35c5636284b36a6b9f3d2faefe379 This demo workspace remains nascent, so please let me know if you have questions about particular types of resources.
Excellent tutorial, William! Is there any away to incorporate task completion date to the tasks database? Any way to store the date the task has been checked as "Done" so that I can create a Calendar view called "Task Log" and use it as a journal/log for all the previous tasks we completed?
Very useful content. How would you suggest setting up the Archives section? I looked at your template and could not see the overarching structure. Would you suggest setting up parallels of the Areas, Projects and Resources databases? That way you would just move the ones no longer needed into the corresponding archived database. Would love your thoughts on this.
Good question. How you manage archives is really a matter of preference. You can include an Archive property (Checkbox) or an Archive option within your Status property, then filter it out of all of your views. Or, you can have an Archive database, where you move completed items.
@@WilliamNutt I like the Checkbox idea. That way I can keep everything together and then filter the views. My only concern longer term is slowing down the system once I get a WHOLE bunch of items in any particular database. Thanks.
Hi William, thanks for the great video! I would like to seek for your opinion on where some of the information should be stored, Area page or master notes. I am struggling to find the best setting myself as I feel I should put all supporting info/reference info in the resources table and then just create the linkage in each project or area tab. However, as I have quite some work projects and personal stuff, my concern is that the master resource database will get too lengthy. I saw in your setting that you would put all the area related info in the resources page and the just create a link in the area page to show those info. However, in your project, you stored project related info under each project(e.g. Blue Ribbon bar) instead of in the resources. What's your criteria/rational on this setting?
Thanks Bradley. Initially, this can be a challenging exercise, but it'll come more naturally as you establish a rhythm. Generally, if a resource is project-specific, I add it within the Project. Otherwise, I add it to the master Resources database and "relate" it to the Area.
Beautiful. One small difference I noticed between your video (or was it the blog post?) and the workspace you shared is that the project's "Status" property is a Select in your blog (something like "Planned", "Completed", etc), and a clever formula in your workspace which computes its value based on the project's "End" date, which itself is computed from the "Deadline" property of the associated tasks. Very neat. However, a Kanban view can no longer be created on that "Status" property once it's a formula, and sorting by it is also trickier because it becomes alphabetical sorting, as opposed to a sort by the order the Select options are arranged (which can mimic a workflow Planned -> Active -> Completed). Which way do you ultimately prefer for this property, if I may ask? Thank you.
Very well done and informative. I find putting the clients into your areas seems not intuitive to me, as in one client gets one area. The definition in the PARA system of areas is a bit slippery to me, unlike projects, resources, and archives. If you have hundreds or thousands of clients, doesn't that preclude putting them all in the areas list which is meant to define high-level categories of operations, like Finance, or HR? I really appreciated the well thought out video and high content level.
zenbotz Absolutely. It just depends on your nature of work. My firm has expansive partnerships with just a few clients at a time, so I find that adding them as areas works well.
Can someone Help me with the Areas stuff I have added my areas but not sure what sould I put in the area or I should just link my Resources to areas. ?
I'll bite: how would I create a calculated progress property in my Projects DB? I thought it would be something along the line of count( prop("Tasks") == "Completed" ) / count( prop("Tasks") ) but it looks like "count" doesn't exist in notion. I'm also not sure I've for the prop("") == "" right, I'm assuming it filters?
Thanks John. It's actually a hidden Rollup property (which allows you to choose the percent of checked checkboxes) combined with a Formula property (just to add the "Complete"). Take a look at this tweet and let me know if you have any other questions: twitter.com/WilliamNutt/status/1227351405360492547
Hi, at around 9:00 you set up a project template that is pre-popluated with a linked task database. How do you set up that linked task database inside the template to filter only the tasks associated with that new project? Is that a manual process? Create a new project off the template, then remember to set up a filter for the linked task database? Thanks for the amazing content btw!
Thanks Chad. Great question. You'll need to create the database unfiltered, then manually filter it for each new project. It might be helpful to add a Callout block above the database to remind you to filter the database, then you can delete the Callout block after implementing each filter.
Another great question. In order for the tasks to be part of the master Tasks database, a new template cannot create new tasks. You might consider creating "placeholder" tasks, which you can easily duplicate when you create each new project.
You can include a "Complete" (Checkbox) property within your Tasks and Projects databases. Then, your "access points" can exclude those. At the moment, I'm deleting completed tasks and sending completed projects to a master Archive database. Great questions. Thanks again, Chad.
Thanks for this. It's great! Can you tell me the best way to add existing pages to the various databases. As an example, I have some pages under 'Areas' in my old system. I want to move them into the database for 'Areas' as I've created it based on this video. But the page will not actually add to the database. The best I can do is get it into the same workspace. Thanks ... Matt
Thanks Matt. Great question. Once your page is in the new workspace, you can use the "Move To" option and choose your "Areas" database. With the page open, you can access the "Move To" option from the ••• menu at the top-right. Alternatively, if you drag the page into your sidebar, you can easily drag it into the "Areas" database. Let me know if a quick video demo would help.
@@michelelanzara945 In this quick demo, I move "Demo Page" from the Nutt Labs workspace to the Resources database of the Loggerhead Labs workspace: drive.google.com/open?id=1eF8SkjPeu1mLX5FrS2qqnnSABtHGlIcH If that popup at the end is confusing, it's just opting not to disrupt the sort settings in the Resources database.
Sorry, I'm no expert in Fortes PARA system but I'm 90% you have got your definition of Areas wrong. According to him Area is where you put stuff that is ongoing and will never end, it didn't have a defined end target like projects. For instance a weekly monthly etc job you have to do.
Thanks for the video! Say I want a client to be able to add projects to the database, how do I prevent exposing our whole database? Since it is just one big database storing all projects from all clients, there seems to be no way to achive that. Which brings me to another problem: Different projects require different attributes. Sure I can just add all necessary attributes to the projects database and switch them on/off in the filtered views but still they all show up on the top of a project page. We could get around all this, if there would be an option to combine databases. That way I could set permissions and attributes just as necessary. Is there some hack to do so?
Both excellent points - thank. Unfortunately, there's no way to share a database view without sharing the full database. I typically maintain an independent, high-level snapshot with a client, then use my master Projects database for the _real_ management. For the varying attributes, or properties, you'll want to include the shared properties in the database. Then, you can include the independent attributes in the page body. Consider creating a template for each project type. Not the most ideal solutions, but certainly workable as Notion continues to introduce new features and capabilities.
Hi @william Nutt, Im wondering how did you make the column for the table of contents small, When i linked database to that page the column of table of contest is on all the page make it shorter for the project to display.
Hello William. Great Video! Thanks for sharing your hard works. When I try to reach the sample workspace, it says that I should be a member of LoggerHead Labs. Would you please add me as a member?
Thanks Imran. In fact, this approach is designed to reduce admin. With such a well defined organizational structure within master databases, information can expand widely while remaining properly placed and easy to access through views and filters. Without such a system, information invariably becomes unmanageable over time.
how to make a unaccecable for new members and or makeit restricted for one department only or for one member only a onemember would only see a view for his role only
When databases contain a Person property, you can filter for "Me." Then, the signed-in users will see only the items where they appear in that property.
Wow, I've been watching a ton of videos and trying to wrap my head about Notion + Para. You've figured it out in a way that makes complete sense.
Thank you. Be sure to see the updated version: ruclips.net/video/DFW1-vcG-8s/видео.html
One of the only really helpful videos about Notion
Well, this thing looks and feels like a solid information system that can only be replaced by an internal website. It unites project management and a knowledge base. I love Notion, the only things that keep it from becoming huge are the lack of public API and the inability to have a local Notion server for the enterprises to use.
It's been 2 years, the API is here and I'd love to see your other idea come to fruition.
Speechless! I will be implementing this strategy ASAP. Thanks a lot for this upload. Outstanding!
Delighted to hear it. Thanks Joshua.
Love the design/layout William. Very clean and not overly complicated like some other Notion setups. Looking forward to seeing your future work!
Quick question: at 5:05 you talk about using a formula within the projects database to calculate percentage complete from the tasks database. Have you got a video or a description about how that is best done? Thanks in advance.
eddie141987 Thanks Eddie. It utilizes a Rollup property. Take a look at that and let me know if you have any trouble.
Thanks for the video help, it provided great structure on how we can setup Notion for our team collaboration (or at least the framework).
Thank you. Be sure to see the updated version: notion.vip/bulletproof
This is SO good! Thanks for sharing, i'll definitely implement this to my workspace :)
Thanks Rebeca. Definitely be sure to consider joining Notion A-to-Z: premier.notion.vip/a-to-z
Thank you for recording this video. I thought I had it down when I participated in your recent crowdcast. However, after watching this video I realized I made my setup way to complicated. Now, I know what I need to do to simplify my system so that it can work for my needs.
Glad to hear it, Christopher.
Absolutely amazing, learning and improving a lot with this product!
jgojiz Thank you. Be sure to see the updated version: ruclips.net/video/DFW1-vcG-8s/видео.html
Great video William. Appreciate you helping out the Notion community like this. Quick question if I may. Following a similar setup to the one you outlined but using the example of being a furniture maker . Typically one would have a number of projects on the go, each with a large number of tasks associated with them. What I’m looking for is a very efficient way to input a number of tasks, typically as they come to mind, and then be able to efficiently order them in the correct sequential order. As the project moves from the initial planning phase through to the actual making/implementation phase many more tasks will spring to mind that need inputting into the correct sequential position. Finally when the project is completed one would end up with a complete “schedule of works” if the project was ever repeated. I wondered whether you’d made any videos that touched on this kind of thing, really focusing on quick task entry and having a step by step sequential schedule of tasks. Many thanks again
Thanks for the kind words, Mark. Where these tasks lists will resemble one another from project to project, I definitely recommend creating templates as much as possible:
www.notion.so/Database-templates-454ed5ab5bd24226b58d176697bd7e10
For these templates, you can have "placeholder" tasks that you can quickly duplicate, then "relate" to the new project.
For one-off projects with unique collections of tasks, the fastest way to add tasks is through a Table view. You can type the task as the last item in the table, then hitting Return/Enter will automatically create a new item for rapid entry.
Of course, for both of the above options, you're using a view of the master Tasks database.
If that's too complicated for you, you could avoid the master Tasks database and instead use an independent Tasks database for each project template. That will allow you have the tasks prepopulated without having to duplicate and "relate" them.
So recapping, three approaches:
1. Create templates wherever possible, where "placeholder" tasks exist within the "view" of the master Tasks database. Each time you use the template, you'll duplicate the "placeholders" and "relate" them to the new project.
2. Rapidly enter new tasks within the filtered Table "view" of the master tasks database.
3. Forgo the master Tasks database and instead have an independent Tasks database for each project, which will allow you to prepopulate all tasks (without duplication).
thanks for this video really helpful with my agency workspace setup
i have seen many videos
yours is the simplest so far
but how can we manage things like giving the access for some table and for some team members
i dont wanna share my whole workspace with them
so can you show how can we do that for all departments in details please
Thank you. You can selectively restrict access to any database item.
If you'll have many private items, I recommend creating private versions of databases-either for yourself or per Teamspace.
How do you have multiple tables below each other like Tasks, Areas, Projects in the Data Section
Thanks Thomas. They are in-line databases. Sounds like you'd make a great candidate for Notion A-to-Z: premier.notion.vip/a-to-z
Hi there! I love your videos. I just discovered notion and my nerdy self has fallen in love with it. I was hoping of you could help me with something though. I want to make a project database template that will automatically show a view of my resources that have the same Area as the new Project. Is there a way to link the projects and resources through a similar property like the relation to the Area? I'm thinking maybe I would need to have a different project template for each area and just have a filter on the resources database view filtered by that specific area.
Thanks so much. The template can only filter for itself. In other words, you can only filter Resources related to the new project.
Your choice are to:
1. manually adjust the filter after implementing the template for each new project; or
2. use a tool like Zapier or Make to relate the new project to all resources related to the project's area.
Sounds like you'd make a great candidate for Notion A-to-Z. 😃premier.notion.vip/a-to-z
Under Contacts>Clients>Client1, I'd like to create a tasks completion table where the data comes from the master database, and filtered by client name. Then I'd like to share that particular page with client1.
Client1 should be able to change the status of the task, add comments, etc from that page, but must not be able to see data of other clients, nor even any other pages.
***How can I achieve that without sharing the entire master database with all the clients?***
Spent 2 days figuring this out with no luck.
Thank you. Notion does not currently support sharing by filtered view, so you'll need to share tasks one-by-one or create a private Tasks database for the client.
@@WilliamNutt thanks for the reply!
How do you include/Relate the Contacts DB as a Resource (if Resources is another core DB)?
Thanks David. You could use a Relation property to link People with Resources. Sounds like you'd make a great candidate for A-to-Z: premier.notion.vip/a-to-z
Very, very helpful. Thanks!
With Notion adding Teamspaces, how would you imploment Teamspace in to this?
Thank you. You can apply Teamspaces to the Bulletproofing Method in a few ways. The most common is to create "micro" Bulletproof Workspaces-each with its own master databases-for content that should be visable only to certain groups.
@@WilliamNutt Great, will you be updating your Bulletproof Notion Workspace 2.0 with these changes?
@@edvinbjork1481 Bulletproof is evolving within Notion A-to-Z, which will offer a variety of resources related to Teamspaces, including tutorials for incorporating them into the Bulletproof system, with functional demos. premier.notion.vip/a-to-z
This is awesome!!
Thanks Maria. More to come.
Agreed Maria!
Fantastic information!
Hi Will! Love this. Implementing notion within my team @HIVED. I had a question, where do you see tasks going for things that are continuous? that don't have a defined start and end. e.g. Customer questions that need to be answered. or day to day operations / fire fighting urgent issues. A distinct 'project' with a start and end doesn't seem to fit these kinds of tasks. But then, just putting them as a task without a project seems disorganised. I hope that makes sense. My sense is to create 'ongoing projects' that have multiple tasks attached.
Thanks Jack. Bingo - under this version of Bulletproof, the best approach is to create ongoing Projects for these circumstances.
For your customer inquiries examples, however, you might consider and independent database for tracking those tickets.
Also - in newer implementations of Bulletproof, Tasks can be related directly to Spaces (formerly “Buckets”) or Organizations.
Great video William, would you mind if you can share the workspace with us? Curious about the Resource table/page. How can you maintain different types of resources in the same table? Thanks
Thanks Michele. You can access the Data page here:
www.notion.so/loggerheadlabs/Data-20d35c5636284b36a6b9f3d2faefe379
This demo workspace remains nascent, so please let me know if you have questions about particular types of resources.
William Nutt Thanks for sharing the site and the tips/tricks in Notion
Excellent tutorial, William! Is there any away to incorporate task completion date to the tasks database? Any way to store the date the task has been checked as "Done" so that I can create a Calendar view called "Task Log" and use it as a journal/log for all the previous tasks we completed?
So long as marking the task complete is the last change you make to the entry, you could use a "Last edited time" property.
@@WilliamNutt that's what I was thinking!
Very useful content. How would you suggest setting up the Archives section? I looked at your template and could not see the overarching structure. Would you suggest setting up parallels of the Areas, Projects and Resources databases? That way you would just move the ones no longer needed into the corresponding archived database. Would love your thoughts on this.
Good question. How you manage archives is really a matter of preference. You can include an Archive property (Checkbox) or an Archive option within your Status property, then filter it out of all of your views. Or, you can have an Archive database, where you move completed items.
@@WilliamNutt I like the Checkbox idea. That way I can keep everything together and then filter the views. My only concern longer term is slowing down the system once I get a WHOLE bunch of items in any particular database. Thanks.
Hi William, thanks for the great video! I would like to seek for your opinion on where some of the information should be stored, Area page or master notes. I am struggling to find the best setting myself as I feel I should put all supporting info/reference info in the resources table and then just create the linkage in each project or area tab. However, as I have quite some work projects and personal stuff, my concern is that the master resource database will get too lengthy. I saw in your setting that you would put all the area related info in the resources page and the just create a link in the area page to show those info. However, in your project, you stored project related info under each project(e.g. Blue Ribbon bar) instead of in the resources. What's your criteria/rational on this setting?
Thanks Bradley. Initially, this can be a challenging exercise, but it'll come more naturally as you establish a rhythm. Generally, if a resource is project-specific, I add it within the Project. Otherwise, I add it to the master Resources database and "relate" it to the Area.
Beautiful. One small difference I noticed between your video (or was it the blog post?) and the workspace you shared is that the project's "Status" property is a Select in your blog (something like "Planned", "Completed", etc), and a clever formula in your workspace which computes its value based on the project's "End" date, which itself is computed from the "Deadline" property of the associated tasks. Very neat. However, a Kanban view can no longer be created on that "Status" property once it's a formula, and sorting by it is also trickier because it becomes alphabetical sorting, as opposed to a sort by the order the Select options are arranged (which can mimic a workflow Planned -> Active -> Completed). Which way do you ultimately prefer for this property, if I may ask? Thank you.
Sébastien Barré Use them both. 🙂 “Status” should be a Select property, and the Formula should be “Progress.”
Very well done and informative. I find putting the clients into your areas seems not intuitive to me, as in one client gets one area. The definition in the PARA system of areas is a bit slippery to me, unlike projects, resources, and archives. If you have hundreds or thousands of clients, doesn't that preclude putting them all in the areas list which is meant to define high-level categories of operations, like Finance, or HR? I really appreciated the well thought out video and high content level.
zenbotz Absolutely. It just depends on your nature of work. My firm has expansive partnerships with just a few clients at a time, so I find that adding them as areas works well.
Clients could be an area itself - that way you have them together. And then you can reference them in both finance and HR or support.
Can someone Help me with the Areas stuff I have added my areas but not sure what sould I put in the area
or
I should just link my Resources to areas. ?
Effective and simple
thanks for sharing this video!!
My pleasure, Nasi. I'm glad you found it useful.
I'll bite: how would I create a calculated progress property in my Projects DB? I thought it would be something along the line of count( prop("Tasks") == "Completed" ) / count( prop("Tasks") ) but it looks like "count" doesn't exist in notion. I'm also not sure I've for the prop("") == "" right, I'm assuming it filters?
Thanks John. It's actually a hidden Rollup property (which allows you to choose the percent of checked checkboxes) combined with a Formula property (just to add the "Complete"). Take a look at this tweet and let me know if you have any other questions: twitter.com/WilliamNutt/status/1227351405360492547
Thanks for the great video! Is it possible to link Resources to more than one project? Could that be done with Tags?
Definitely. With the Relation property, you can choose multiple projects.
Hello, excellent video. How do you hide the horizontal scrollbar?
Lewin Viola Thank you. Can you please screenshot the scroll bar you want to hide?
Hi, at around 9:00 you set up a project template that is pre-popluated with a linked task database. How do you set up that linked task database inside the template to filter only the tasks associated with that new project? Is that a manual process? Create a new project off the template, then remember to set up a filter for the linked task database? Thanks for the amazing content btw!
And is there a way to pre-populate a project template with tasks?
Last question. I promise. I love the idea of this workflow, but how would you archive a project if all of the tasks and pieces are so spread out?
Thanks Chad. Great question. You'll need to create the database unfiltered, then manually filter it for each new project. It might be helpful to add a Callout block above the database to remind you to filter the database, then you can delete the Callout block after implementing each filter.
Another great question. In order for the tasks to be part of the master Tasks database, a new template cannot create new tasks. You might consider creating "placeholder" tasks, which you can easily duplicate when you create each new project.
You can include a "Complete" (Checkbox) property within your Tasks and Projects databases. Then, your "access points" can exclude those.
At the moment, I'm deleting completed tasks and sending completed projects to a master Archive database.
Great questions. Thanks again, Chad.
Thanks for this. It's great! Can you tell me the best way to add existing pages to the various databases. As an example, I have some pages under 'Areas' in my old system. I want to move them into the database for 'Areas' as I've created it based on this video. But the page will not actually add to the database. The best I can do is get it into the same workspace. Thanks ... Matt
Thanks Matt. Great question. Once your page is in the new workspace, you can use the "Move To" option and choose your "Areas" database. With the page open, you can access the "Move To" option from the ••• menu at the top-right. Alternatively, if you drag the page into your sidebar, you can easily drag it into the "Areas" database.
Let me know if a quick video demo would help.
William Nutt quick demo video will be fantastic
@@michelelanzara945 In this quick demo, I move "Demo Page" from the Nutt Labs workspace to the Resources database of the Loggerhead Labs workspace:
drive.google.com/open?id=1eF8SkjPeu1mLX5FrS2qqnnSABtHGlIcH
If that popup at the end is confusing, it's just opting not to disrupt the sort settings in the Resources database.
can I use each page for Projects, Tasks, Areas, & Resources? I do not like inline databases
Certainly - just add Table - Full Page for each.
Sorry, I'm no expert in Fortes PARA system but I'm 90% you have got your definition of Areas wrong. According to him Area is where you put stuff that is ongoing and will never end, it didn't have a defined end target like projects. For instance a weekly monthly etc job you have to do.
As the experts say, there are no "PARA police." Like Bulletproof, it's a guiding framework to be adapted for your unique needs.
@@WilliamNutt fair enough, wasn't saying your use of it doesn't work for your implementation rather that maybe saying it was para based!
Thanks for the video! Say I want a client to be able to add projects to the database, how do I prevent exposing our whole database? Since it is just one big database storing all projects from all clients, there seems to be no way to achive that. Which brings me to another problem: Different projects require different attributes. Sure I can just add all necessary attributes to the projects database and switch them on/off in the filtered views but still they all show up on the top of a project page. We could get around all this, if there would be an option to combine databases. That way I could set permissions and attributes just as necessary. Is there some hack to do so?
Both excellent points - thank. Unfortunately, there's no way to share a database view without sharing the full database. I typically maintain an independent, high-level snapshot with a client, then use my master Projects database for the _real_ management.
For the varying attributes, or properties, you'll want to include the shared properties in the database. Then, you can include the independent attributes in the page body. Consider creating a template for each project type.
Not the most ideal solutions, but certainly workable as Notion continues to introduce new features and capabilities.
Nice I still dont know hot to do this thx
What app are you using for this presentation?
Loom + Clipchamp
Hi @william Nutt, Im wondering how did you make the column for the table of contents small, When i linked database to that page the column of table of contest is on all the page make it shorter for the project to display.
Thanks Diego. I don't quite understand your question. Do you mind linking to a screenshot of your issue? With that, I'll be happy to explain.
Hello William. Great Video! Thanks for sharing your hard works. When I try to reach the sample workspace, it says that I should be a member of LoggerHead Labs. Would you please add me as a member?
Thanks so much, Berkay. Members of Notion A-to-Z can access the Bulletproof Workspace and a multitude of other resources: premier.notion.vip/a-to-z
Great work William. Sounds like a lot of admin though, would you agree?
Thanks Imran. In fact, this approach is designed to reduce admin. With such a well defined organizational structure within master databases, information can expand widely while remaining properly placed and easy to access through views and filters. Without such a system, information invariably becomes unmanageable over time.
how to make a unaccecable for new members and or makeit restricted for one department only or for one member only
a onemember would only see a view for his role only
When databases contain a Person property, you can filter for "Me." Then, the signed-in users will see only the items where they appear in that property.
Is there a template of this to duplicate?
Indeed, you can access the Loggerhead Labs demo here: www.notion.so/loggerheadlabs/Home-Base-33b8946d04ea4026a8b69c65e8baffaf
This is me