The Documents page inside a project brings its files, controlled documents, required uploads, and pending reviews into one workspace.Use it to organize project records, access drawings and release files, assign upload responsibilities, and follow document reviews without leaving the project.The starting folder layout comes from the Folder Structure selected when the project is created. Ordinary project folders can then be managed according to their permissions, while system-managed locations remain protected.
Navigate to:Projects → Select a project → DocumentsThe Project selector at the top identifies the current project and lets you switch between accessible projects. The project header also displays the Phases selector.Use the folder tree and breadcrumb to confirm the document location before uploading, downloading, or making changes.
Related article: See Documents in the main module for shared file-management rules and the Workflow, Naming, and Folder Structure libraries.
Browse the project's folders, upload normal files, create controlled documents, and inspect versions and activity.
Required
Find accessible documents in this project awaiting a first upload or a corrected version after review.
My reviews
Find this project's documents whose active review step is assigned to you.
Required and My reviews cover the current project, not just the folder selected in Files. Their badges show the total matching queue, not only the cards on the displayed page.The Workflow, Naming, and Folder Structure management tabs are available under Main menu → Documents, rather than inside the project page.
When creating a project, select a reusable folder template in the required Folders Structure field.
1.
Navigate to Projects and click Add Project.
2.
Complete the project details and select an active Folders Structure.
3.
Click Create Project.
4.
Open the new project's Documents page to review its folders.
Fabritec creates the project's main Job Number folder and copies the selected template's folders and configured settings into it. These settings can include permissions, folder visibility, workflows, default reviewers, and naming conventions.For example, a template may create Contract, Assembly DWG, Single DWG, and CNC folders. The actual names and hierarchy depend on the selected template. System-managed branches are handled separately.Authorized users can choose Create New Folder Structure from the selector to open structure management in a new tab. After creating and activating the template, return to the project form, use Refresh, and select it.
Important: A folder structure is copied at project creation. Later template changes do not update existing project folders or settings. Make authorized changes directly in the existing project's Documents page instead.
Project Documents contains locations with different operating rules.
Location
How it works
Project's Job Number folder
The main project container. Its identity is protected. Eligible users can create ordinary child folders, and users with Folder Control can manage its permissions. Direct file uploads and controlled-document creation are not available at this level.
Ordinary project folders
Folders copied from the template or created by authorized users. These support normal file and document operations according to permissions, workflow settings, naming rules, and locks.
System-managed branches, such as Releases
Protected locations managed through their owning Fabritec workflows. They remain read-only through Documents, including their nested folders and files.
The Job Number folder cannot be renamed, copied, cut, moved, or deleted through Documents.Users with Folder Control or View, Download, Upload & Edit can create folders directly beneath it. Lower folder permission levels do not grant that action.Having permission to manage the root does not allow users to change protected system branches. It also does not make every ordinary child folder editable; each child's effective permissions still apply.
A protected location displays a lock or protection indicator and a system-managed notice.You can browse and download accessible content, but you cannot use Documents to upload, rename, move, copy, delete, review, change permissions, or remove system locks there. Folder Control and administrator access do not override this protection.To work with release or item files, use the relevant revision or item workflow that owns them.
Do not upload release packages directly into Releases from Documents. Use ordinary project folders for manually managed files and the owning workflow for system-managed content.
The folder tree on the left starts at the project's main folder. Expand or collapse folders to navigate through the project hierarchy.The breadcrumb above the contents identifies the current location. Use the folder-panel toggle to show or hide the tree.Some ancestors may appear only so you can reach an accessible subfolder. Seeing one of these navigation-only folders does not grant access to its files or management actions.
Enter a name in Search this folder to search the selected folder and its subfolders. Search returns only accessible items and matches names, not text inside documents. The In folder column identifies a search result's containing folder.Use the sort control to arrange items by the available criteria, including name, size, version, and dates. Use the view toggle to switch between the table and file cards, and click Refresh to reload the contents.
Accessible items in the current folder, including its immediate subfolders.
Approved
Controlled documents whose review workflow is complete.
In review
Controlled documents with an active review step.
Changes requested
Controlled documents returned for correction and awaiting a replacement upload.
Documents awaiting their first upload are also listed in Required.An eligible controlled document may show a quick-action icon beside its name for Review, Upload first version, or Upload new version when changes are requested. It opens the same authorized action used in the corresponding tab.
The latest uploaded version is not necessarily approved. Check both Version and Status before using a controlled document.
Open the project's main folder or an ordinary parent folder where you have the necessary access.
2.
Click New folder.
3.
Enter the required Folder name and choose whether to enable Visible to everyone.
4.
Click Create folder.
You can also use New subfolder from an ordinary folder's three-dot menu.Use valid, descriptive names. Reserved characters such as \ / : * ? " < > | are not allowed. System-managed locations cannot be used as ordinary folder-creation destinations.
A normal file is stored without a review workflow. Use this option for project records that do not require a controlled review process.
1.
Open the appropriate ordinary project folder.
2.
Click Upload files.
3.
Select the files or add them through the upload dialog's drop area. Use folder selection to upload a nested folder hierarchy.
4.
Start the upload and check each file's final result.
Uploads must satisfy the folder's naming rules, permitted file types, storage allowance, and upload limits. A normal-file upload does not start a review workflow merely because the folder has a workflow assigned.Without a naming convention, duplicate names receive a suffix rather than overwriting an existing file. In a naming-controlled folder, noncompliant or duplicate names are rejected.A folder configured as Documents only blocks normal-file uploads. Use New document and its version-upload process instead.
Keep the upload dialog open until processing finishes. Finalizing is not yet a successful upload. For a mixed-result batch, use Retry failed instead of uploading successful files again.
An authorized folder controller can use the folder's three-dot menu to Assign workflow and Assign naming convention.A workflow defines the sequence of review steps. It can be assigned directly or inherited from a parent. Optional default reviewers prefill the reviewer selections for future documents.A naming convention defines the required filename pattern. Naming conventions are not inherited; assign one separately to each folder that needs it. Applying a convention checks existing filenames and does not automatically rename noncompliant files.These are settings for the actual project folder. To create or maintain reusable workflow and naming definitions, use their libraries under Main menu → Documents.
A controlled document records an upload responsibility, review workflow, versions, and a linked task. You can create it before the file is ready.The destination must be an ordinary folder with an effective workflow. You also need the relevant document-management permission and folder upload access.
1.
Open the destination folder and click New document.
2.
Complete the document information below.
3.
Check the applicable workflow and assign at least one reviewer to every step.
4.
Click Create document.
Field
What to enter
Name
The required document name, following the folder's naming convention where applicable.
Estimated hours
A nonnegative estimate. Leave it at 0 when no estimate is needed.
Start date
An optional planned start date.
Due date
An optional due date. When both dates are entered, the due date cannot precede the start date.
Responsible user
The person responsible for supplying the file.
Step reviewers
At least one reviewer for each workflow step. Review any prefilled defaults before saving.
The document appears in the project's Required tab, and Fabritec immediately creates a linked upload task for its responsible user. Review begins only after the first version is uploaded.
An eligible normal file can be converted into a controlled document using its conversion action.Complete the document information, responsible user, reviewers, and positive actual work hours. The existing file becomes the current document version, and review starts at Step 1.Conversion requires an effective folder workflow, the necessary permissions, and an unlocked, non-system file.
Conversion is one-way. Controlled documents cannot subsequently be copied, moved, or deleted through normal-file actions.
Use View for supported previews or Download to retrieve the file. Both require the appropriate download access.The normal download action retrieves the latest version. Open Version history to inspect and download a specific earlier version, where permitted.Version history can show the version number, uploader, upload date, size, actual hours, change reason, lock information, and review decisions. Decisions identify the reviewed version, step, reviewer, outcome, date, and optional comment.A replacement upload preserves previous versions and their review history. Individual retained versions cannot be edited or deleted through version history.Selecting multiple items or a folder and clicking Download creates a ZIP of permitted, visible latest files. It is not a complete version-history or workflow backup.
Use the three-dot menu or selection toolbar for the actions allowed by the selected content and your permissions.
Action
Important behavior
Rename
Changes an eligible item's name. Naming rules and locks still apply. A controlled-document rename also updates its linked task title.
Copy / Cut / Paste
Copies or moves eligible normal files and ordinary folders. Source and destination permissions apply. Controlled documents, protected content, and folder subtrees with controlled-document dependencies cannot be transferred this way.
Details
Shows read-only information about the item, its location, settings, and effective access.
Edit metadata / Edit reviewers
Updates eligible controlled-document information or unfinished-step assignments. Completed review decisions are not rewritten.
Lock / Unlock
Available to authorized folder controllers for eligible versions. A locked latest version blocks changes and review; system locks cannot be removed.
Delete
Removes eligible ordinary content, subject to permission and protection checks. Controlled documents cannot be deleted through the normal file-delete action.
Selecting an item's checkbox displays the selection toolbar. Select all items can include matching items beyond the displayed page, so check the selection before applying an action.
Deletion warning: Deleting one normal file is a soft deletion; its retained content continues to count toward storage. Deleting an eligible ordinary folder permanently removes its eligible nested contents and recorded versions. Protected content and controlled-document dependencies can block folder deletion.
The Required tab shows accessible documents anywhere within the current project that need an upload.A document appears here when its first file has not been uploaded or its current review was rejected and a corrected version is required. Selecting another folder in Files does not narrow this queue.Cards show the document's name and containing folder, responsible user, planned hours, due date, upload state, and available action. Expand Workflow progress to inspect its review steps.
Choose the file and enter Actual hours greater than zero.
4.
Submit the upload and confirm that it succeeds.
A change reason is not required for the first upload.Fabritec creates v1, starts Step 1, and assigns the existing linked task to the active reviewers. The document leaves Required and becomes In review.
Enter only hours not already recorded in the linked task. Upload hours are added to existing preparation logs; they do not replace them.
A returned document displays Revision needed, View comments, and Upload new version.
1.
Click View comments to inspect the rejected version's review decision.
2.
Correct the file according to the feedback.
3.
Click Upload new version and select the corrected file.
4.
Enter a Reason explaining the change and positive additional Actual hours, then submit.
Review comments are optional, so a decision may have no accompanying comment.After a successful upload, the version number increases, the document leaves Required, and the same workflow restarts at Step 1. Earlier decisions remain in history.Replacement uploads require Upload Document Versions, folder upload access, and an unlocked latest version. Responsibility for the document alone does not override those checks.
A document whose workflow is already Approved and complete cannot be reopened through another version upload or another workflow assignment.
No uploads are waiting means no accessible document in this project currently needs an initial or corrected upload. It does not mean the project contains no documents.
The My reviews tab lists the current project's documents waiting for your decision on the active workflow step.A document assigned to you at a future step does not become reviewable until that step is active.
Open My reviews and check the document's name, folder, current step, and due date.
2.
Use View or Download to inspect the file.
3.
Click Review and confirm the document, version, and step.
4.
Add an optional comment and select Approve or Reject.
Only an assigned reviewer of the active step can submit the decision. Document-management access or Folder Control does not authorize approval on another reviewer's behalf.
Completes that step and activates the next. The linked task moves to the next reviewers and configured task status.
Approve the final step
Marks the document Approved, completes its workflow and linked task, and clears the task's assignees.
Reject
Marks the document Changes requested, returns the linked task to the responsible uploader, and places the document in Required for correction.
Rejection does not automatically lock the file. Review pauses until a replacement is uploaded, at which point it restarts from Step 1 rather than the rejected step.Steps run sequentially. When several reviewers are assigned to one step, only one decision is applied to that step and version; another reviewer cannot submit a second decision after it has been completed.A locked latest version or system-managed location prevents review even when you are assigned.
Access to Project Documents requires View Files. The actions available inside it also depend on effective folder permissions, document assignments, and system or version locks.The same restrictions apply whether you reach a project folder from the project's Documents page or through the Projects branch in the main Documents module.
Open the folder and click Permissions, or choose it from the folder's three-dot menu.
2.
Use Add department or Add user to add the relevant entries.
3.
Choose each entry's permission level and review Visible to everyone.
4.
Click Save.
Only users with Folder Control can save these settings. You cannot remove your own Folder Control grant.
Permission level
Access provided
Folder Control
View, download, upload, edit, and administer eligible content and folder settings, subject to system restrictions and additional permissions.
View, Download, Upload & Edit
View, download, upload, edit eligible content, and create or rename ordinary subfolders. Does not grant folder administration.
View, Download & Upload
Browse, download, and upload without editing or administration.
Upload & Download
Upload and download, with visibility of the folder and file information.
Upload Only
Browse the folder and file information and upload content. Download and preview are not granted.
View Only
View and download accessible content, including supported previews. Does not allow upload, editing, or administration.
View Only includes downloading. Folder access does not replace the separate system permissions required for controlled-document creation, configuration, or version uploads.
A folder without direct permission entries inherits from the nearest parent with grants. Direct entries replace inherited grants for that folder. At the same permission source, an individual user grant takes precedence over a department grant.Visible to everyone gives users with View Files read/download access to the folder's accessible contents. It does not grant upload or edit rights, create anonymous access, or automatically make subfolders visible.Turning it off does not remove access granted directly or inherited from a parent.During an active review workflow, versioned controlled documents have additional visibility restrictions for the creator, responsible user, configured reviewers, and eligible folder controllers. After final approval, normal folder visibility rules apply.
A controlled document uses one linked task throughout its upload and review lifecycle.The task starts with the responsible uploader, passes to each active review step's reviewers, returns to the uploader when changes are requested, and completes after final approval.Document dates and estimated hours synchronize with the linked task through authorized edits. The document lifecycle controls the task's status; changing a task status manually is not a substitute for uploading or reviewing the document.Preparation time can be logged before the first upload. Later work logs are attributed to the relevant document version, and upload hours are additional to time already logged.Document notifications help assigned users follow upload and review handoffs. Their links still enforce the current permissions and document state.For detailed task synchronization, work-log rules, and notification preferences, see the main Documents article.
Confirm the project and destination before uploading. Use the Project selector, folder tree, and breadcrumb to avoid placing files in the wrong location.
Choose the folder structure carefully at project creation. Review its folders and access settings; later template changes will not update the existing project.
Keep manually managed files in ordinary folders. Use the owning revision or item workflow for Releases and other protected content.
Use controlled documents when review is required. Confirm the responsible user, workflow, and reviewers before submission.
Check Required and My reviews regularly. Address outstanding uploads and active review steps promptly, and provide clear comments when requesting changes.
Check both version and approval status. Keep corrections within the same incomplete controlled document using Upload new version, and record only hours not already logged.
Review access and selections before sensitive actions. Check inherited permissions before sharing and nested contents before deleting an ordinary folder.
Why is Upload files disabled at the Job Number folder?#
The project's main folder is a protected container, not a direct upload destination. Open an ordinary child folder where you have upload access. A Documents only folder requires the controlled-document process instead.
Why can I manage an ordinary folder but not Releases?#
Releases is system-managed and read-only through Documents. Folder Control and administrator access do not override that protection. Use the workflow that owns the files.
Why does Required show documents from another folder?#
The project's Required queue includes accessible documents throughout the project's folder hierarchy. It is independent of the selected Files folder.
Your step may not be active yet, another assigned reviewer may already have decided it, or the document may be awaiting a replacement, locked, completed, or inaccessible under its current permissions.
Why did editing the folder template not update this project?#
Templates are copied when projects are created. Edit the actual project's ordinary folders and settings, with the appropriate permissions, to change an existing project.
