nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Folder view in repository

Tuffer_Harris

I would like to see the option of viewing the repository in a folder structure. It doesn't have to change how Ironclad technically stores the contracts in the backend, but I should be able to choose that I want view and browse the repository contracts as if they were in a folder structure. It could allow you to dynamically designate how they are organized (Customer top folder, contract parents subfolder, then contract child subfolder, etc.) and then show it to you like a standard file structure. This can be a more intuitive way to search for somethings, and it also helps to find a customer whose name may be spelled wrong, or abbreviated, or provide a more global overall view of all the contracts you have for a certain category.

We have teams that use other systems to store contracts and won't move over to Ironclad simply because they want a folder view to browse.

Find more posts tagged with

Status: None

Comments

Tuffer_Harris

Just wanted to re-emphasize this. And maybe folder view isn't the solution but we have been trying to consolidate where contracts are stored and accessed by other departments, and they need a much cleaner and direct UX experience to find contracts if we want to stop other departments from storing executed contracts in their own files. They have very simple searches ("I need the active MSA for xyz customer" or "Show me the current SOW"), and the process of searching with a name and getting a big list then having to figure how to filter, what the right field names are, and go through all the options is a roadblock.

Erin_Till

Thanks for bumping this @Tuffer_Harris! This is great feedback, and I’ve shared with our internal teams and will follow-up with any updates or recommended best practices with existing capabilities.

Sharon_Donnigan

@Erin_Till, thanks for digging deeper into this Idea. @Tuffer_Harris, awesome suggestion!

Zachary_Merson

@Tuffer_Harris @Erin_Till We have the same problem and have been disappointed to hear that Ironclad still doesn't have a solution for this. The lack of foldering/nesting capabilities is very frustrating and requires us to continue maintaining SharePoint as our contract repository.

Christopher_Yee

We're achieving this by leveraging the one drive integration and then using a script to move everything from the one drive account into SharePoint. Not ideal as it's outside of Ironclad and it's a finnicky integration (though one benefit is that you can give repository access to non-license holders this way).

Tuffer_Harris

That tells me its a sought after feature 🙂

Christopher_Yee

Yes, to me, the repository is Ironclad's biggest limitation.