Triark Cloud uses a structured, logical model to help you manage technical documentation in a consistent and secure way.

Below, you’ll find a clear introduction to the core concepts, so you can feel confident using Triark from day one.

📁 Projects, Documents, and Revisions

Projects
Projects act as the main containers in Triark. All your documentation, tasks, and workflows belong to a project. Projects give you a way to organize work by customer, location, or discipline, while controlling who can see or change information.

Documents
A document in Triark is not the file itself — think of it as a container or folder with its own metadata, such as category, status, or owner. Each document holds multiple revisions of the same technical information over time. This way, you can manage metadata at a higher level (the “document”), while keeping a full revision history within it.

Revisions
Revisions are where the actual files live. Each time you update a file, you add a new revision inside the same document. This guarantees a clear, traceable history of changes, approvals, and sign-offs without losing older versions.

🔗 What is a Reference?

References are a way to connect related data within Triark.

For example, a procedure document might reference a product standard, or an inspection checklist might reference a quality guideline.

References help you build a visible network of relationships across documents, products, and standards, so everyone knows how things connect.

📂 Folder Structures & Metadata

Triark supports traditional folders to group your documents in a familiar tree-like structure.

In addition, metadata (like category, document type, or custom fields) gives you powerful filtering and search capabilities across your documents and revisions.

✅ Folders organize logically
✅ Metadata improves search and reporting

👥 Permission Roles

Triark includes three main role levels by default:

• Admin → manage everything, including permissions
• Writer → edit, upload, revise, and collaborate
• Reader → view and download approved revisions

These roles can be fully customized, and security rules can be refined to match your team’s exact needs.

🔒 Security Philosophy in Triark

Triark is designed for secure, role-based access:

✅ Permissions are tied to projects, folders, and documents
✅ All user actions are logged for traceability
✅ Approvals and sign-offs are structured and auditable
✅ Flexible rules let you adapt to any security or compliance environment

“By understanding how projects, documents, and revisions work together, you’ll be ready to manage complex technical data with confidence.”

‍