Sources & Folders
Create, organise, and manage sources and folders in your workspace.
Sources are the containers that hold artefacts: requirements, hazards, verification cases, evidence rows, decisions, or any other regulated record your workspace tracks. Folders organise sources without changing the artefacts inside them.
Modules navigation
Open Modules from the workspace navigation to work with sources and folders. The page uses a compact top bar with a left Modules tree drawer. Open the drawer to move through folders, sources, source views, direct-shared restricted sources, and any unfinished imports that belong to you.
The main area stays focused on the thing you selected: the root Modules table, a folder table, a source table, a saved source view, an artefact selection, or an import workbench. On smaller screens, the same Modules tree opens as a sheet and closes after allowed navigation.
People with permission to create source-library items use the action row on the root or folder table to add a folder, create a source, or start an import. The drawer is for navigation and in-progress imports, not a separate place to create hidden data.
Readable module and folder URLs
Modules and folders use readable workspace URLs, such as /workspace/{workspace-url}/sources/modules/{module-url} and /workspace/{workspace-url}/sources/folders/{folder-url}. If a module or folder is renamed, old readable links redirect to the current URL when you still have access.
Visible module and folder headers can show Copy URL after Integrity has loaded the safe route key. Restricted or hidden parent context stays redacted; copying a direct-shared object URL does not grant access to hidden parent folders or modules.
Object details
Selecting a folder, source, source view, artefact, or import context keeps you in Modules and updates the selected object in the top bar. When the selected object has supporting context, the right drawer can show Properties and an Activity placeholder. The root Modules view does not show a right context drawer because it is a workspace-level table, not one selected source-library object.
Properties show display-safe metadata for the selected object. Restricted and direct-shared entries only reveal the context you are allowed to see; hidden folder paths, source names, identifiers, colors, field labels, counts, and parent context stay redacted. Activity is supported for Artefact detail and Review & Discuss today. Source, folder, and source-view object shells may still show an Activity drawer affordance only where a dedicated source-library activity feed is not yet implemented.
Module and folder row selection
Modules and folder tables support session-only row selection. Use row checkboxes, Ctrl-click a row (Cmd-click on macOS) to toggle only that row, Shift-click visible ranges, and the floating Actions bar to work with the current visible selection. Unsupported future commands are omitted rather than shown as disabled placeholders. When no safe selected-row command exists for the object family, Integrity shows generic no-action copy without revealing hidden source or folder context.
Selection is scoped to the current Modules route, source/folder context, and visible rows. Changing source views, routes, filters, or access state prunes or clears the selection without changing saved source views, source defaults, filters, imports, detail drawer preferences, or realtime subscriptions.
Module and folder settings
Module and folder settings open in the route-backed Workspace Settings view instead of a separate object dialog. Use the settings action from a module or folder row, sidebar item, or object header to open the matching settings page.
Module settings include General, Members, External access, Requests, and Logs where available. General controls the module icon, name, kind, identifier prefix, and visibility. Members and External access keep restricted membership, access requests, scoped guest invitations, and active external guests separate.
Folder settings use the same layout for icon, name, visibility, members, external access, requests, and logs. Restricted folders render a display-safe restricted state for people without access; they do not expose hidden names, paths, colors, or member detail.
Changing a module identifier prefix uses a controlled cascade that preserves each artefact number. If Integrity cannot safely map existing identifiers to the current prefix shape, it blocks the change and explains the issue instead of rewriting identifiers.
Lifecycle vocabulary
Integrity uses one lifecycle vocabulary across the Source Library, Trace Schema, baselines, history, and import/report surfaces:
| State | Meaning |
|---|---|
| Active | The source, folder, view, or artefact exists and is available to you. |
| In Trash | The item was moved to Trash and can still be restored. Recoverable Trash states use muted, non-destructive styling. |
| Deleted | The item was permanently deleted. Historical evidence may still show a tombstone so audit trails remain understandable. |
| Restricted | The item exists, but you do not have permission to see its name, identifier, color, or parent context. |
| Unknown | Integrity cannot safely resolve the reference from live rows, tombstones, or explicit status flags. |
Storage fields may still be named is_archived for compatibility, but user-facing source, folder, artefact, note, and view lifecycle copy says Move to trash, In Trash, Restore, Delete permanently, and Deleted.
Move to Trash
Use Move to trash when you want to remove a source, folder, source view, or artefact without permanently deleting it. Items in Trash can be restored, and references to them show In Trash so reviewers can distinguish recoverable state from permanent deletion.
Use Delete permanently only when the item should be removed for good. Permanent deletion creates tombstone display data for audit trails where the app needs to explain what used to be there.
Restricted references
Restricted sources and folders redact their display data for people without access. A table, graph, history entry, or baseline row should show Restricted without leaking the hidden title, identifier, icon color, folder path, or source name.
Archive exceptions
Archived is still the right word for true retirement or evidence concepts, such as retired source templates, disabled kind definitions, archived baseline types, notifications, and evidence archives. Those are configuration or audit records, not recoverable Source Library entities in Trash.