File tags in Marvin help with organizing and grouping files within a project and across projects. These tags can be created based on various categories and shared across the entire repository, allowing users to filter and search for specific files or projects effectively.

Let's talk about tagging your research at a file level.

Each file in Marvin can be tagged based on many different things. For example, this could be based on company type, this case on customer, non customer, right, could be based in this case location session type. The idea is to be able to group together different types of files and tag them differently.

Now, the major advantage, or one of the big ways in which you can use this in an information architecture, is to create shared tags across all of the projects.

What that means is in this case, for example, we have Marvin internal, maybe I call it Marvin Customers. And then I have all of those tags.

Marvin Customers is the name of the group. And then I have all these subgroups based on the customer's name. I can have the same with company type, I've tagged product research and the non tag, I've shared these tags across the entire repository.

What that lets you do is both group projects within a project and then share that kind of grouping across the entire repository. And this shows up when you're doing your cross project or within a project analysis.

Let's showcase this in a cross project. I'm in this cross project analysis, and if I wanted to showcase any kind of I want to see all of the research from tech product, customer type or maybe from a certain group of customer, I can select those and I can apply and then it'll help me narrow down the repository or from individual group of files perspective.

And this is also helpful in doing search, right? For example, if I was to do something like searching for onboarding in the search results, I can say show me only results from when this research was done from a tech product point of view. Now we have been able to narrow down.

So this is the second way to organize your repository at a file level and then you can combine them together like I was both in the cross project analysis, we can say project groups, I want to look at anything from customer marketing. And in terms of the file tags, I'm only looking for non tech companies, and I can start to apply all of these together to search through and filter both from the analysis perspective and search perspective to pinpoint the right project, the right file within a project, the right research within a project — using these combined can really build a really powerful repository.