Unified Project File Management
For developers and project managers, the term "Project Management" often means juggling multiple tools: a Kanban board for tasks, a spreadsheet for budgets, and an external cloud service (like Drive or Dropbox) for artifacts. This fragmentation creates a major operational cost: the time spent searching, verifying versions, and managing security across disparate file repositories.
The Project Resource Management (PRM) Platform was made to defeat this cost by making the project board the definitive source of truth for both activity and artifacts. We've introduced a proprietary Unified Project File Management system that eliminates external file silos.
1. The Problem: Decentralized Project Inventory
Before integration, project artifacts created two major pain points:
- Version Ambiguity: Without a central, secure link, teams constantly waste time confirming if they are working with the absolute latest contract, design mock-up, or scope document.
- Security Gaps: Managing access control for files separately from the project's Role-Based Access Control (RBAC) creates security vulnerabilities and compliance issues.
Our goal was to ensure that if a user has access to a task, they have immediate, secure access to the related files, and nothing else.
2. The Solution: Contextual Artifact Association
Our new feature, visible in the Project Hub's "Project details" view, ensures that files are created and stored precisely where they are relevant, linking the artifact directly to the financial and operational context.
We now have three distinct, automated pipelines for creating tasks (cards) and associating files:
- Direct on the Boards Page: Manual task creation is seamless, allowing users to attach files that are immediately routed to the proper sub-folder.
- Via the Projects Hub: Tasks created here automatically inherit all project-level security settings.
- Client Ticket Automation: A client submitting a ticket instantly creates a task card, beginning the execution flow.
How File Integrity is Maintained:
- Project-Level Repository: On project creation, a dedicated, secure Project Repository Folder is established. All files, notes, and team data are instantly associated here.
- Card-Level Context: When a user adds an attachment to a Card (Task), a unique Cards Folder is automatically created inside the main Project Repository. This guarantees that files are always traceable back to the specific task that generated them.
- Unified Access: All project files—both exiting files and task attachments—can be instantly accessed and managed directly through the Project Hub's details page, providing single-click access for team members.
By unifying the project file inventory under the same robust security and data model that governs time logs and financial budgets, we deliver not just efficiency, but auditable integrity. We are helping teams move past file logistics to focus entirely on execution.
