Atlam Pty Ltd — Intranet

🚀What is this intranet?

This is Atlam's internal hub. It has two main areas:

1

Resources — your file library

Upload and access any company file — policies, service manuals, templates, software installers. Files are stored in Supabase and accessible from anywhere.

2

QMS — your quality management system tracker

Tracks all your QMS documents, their versions, review dates, and relationships. Automatically flags documents that need attention — either because a related document changed, or because annual review is due.

💡The two areas work together: upload a QMS PDF in Resources and the system automatically detects the document ID, checks the version, and asks you to confirm the link — no manual copy-pasting needed.

📋First-time setup checklist

1

Run the QMS SQL migration in Supabase

Go to supabase.com → your project → SQL Editor → paste and run the qms_migration.sql file. This creates the QMS tables and seeds your initial documents.

2

Upload your QMS documents as PDFs

Go to Resources → + Upload. Upload each QMS PDF (e.g. ATL-QMS-001, ATL-QMS-002). The system will automatically detect the document ID in the filename or file content.

3

Confirm the auto-link prompt

After each PDF upload, a confirmation panel will appear showing which QMS document was detected, what version was found, and how it compares to the register. Click Link to QMS register to confirm.

4

Check the QMS view

Click QMS in the top bar. Documents with linked files will now show a View ↗ button that opens the PDF directly.

📤How to upload a document

1

Click Resources in the top bar

Make sure you're on the Resources view, not QMS.

2

Click + Upload

The upload panel will open on the right side of the screen.

3

Fill in the details

Give the file a clear name (e.g. ATL-QMS-001 — Document Control Procedure), a short description, and choose a category.

4

Choose File Upload or External URL

File Upload: drag and drop or browse for a file from your computer. It gets stored in Supabase Storage.

External URL: paste a link to a file already hosted somewhere (e.g. Google Drive, SharePoint).

5

Click Upload Resource

The file appears in the resource list. If the file is a QMS PDF, the system will automatically scan it and show a confirmation prompt to link it to the QMS register.

💡PDFs are automatically optimised on upload — metadata is stripped to reduce file size. For very large files (over 20MB), you'll get a warning suggesting you compress first using Smallpdf or Adobe Acrobat.

📁Categories

Categories help organise your files. The default ones are:

Category	What to put in it
Company Policies	QMS documents, WHS policy, HR policies
Admin Resources	Letterheads, forms, templates
Newsletters	Company updates and announcements
Service Docs	Equipment manuals, technical guides, service bulletins
Software & Setup	Installers, configuration guides, IT tools

💡You can add your own categories at any time using the + Add category button on the Resources view. Consider adding a dedicated QMS Documents category to keep policy files separate.

🔗How automatic QMS linking works

When you upload a PDF in Resources, the system automatically scans the filename and file content for a QMS document ID (e.g. ATL-QMS-001). If a match is found in the register, it reads the version history and shows a confirmation prompt before linking.

1

Upload the PDF in Resources

Go to Resources → + Upload. Fill in the name and category, select your PDF file, and click Upload Resource. The system starts scanning immediately after the file is stored.

2

Review the confirmation prompt

A panel appears showing the detected document ID, its title from the register, your uploaded filename, and a version comparison. The version row will be green (newer), blue (same), or amber (older than register).

3

Check the version history snippet

If the system found a version history table in the PDF, it shows a raw extract so you can verify the version reading was correct before confirming.

4

Click Link to QMS register

Confirms the link. The QMS register is updated instantly — no Supabase visit needed. The document row will show a View ↗ button immediately.

💡The document ID must appear somewhere in the filename or PDF content for auto-detection to work. For best results, name your files consistently — e.g. ATL-QMS-001 Document Control Procedure v1.0.pdf.

ℹ️If no QMS document ID is detected, the upload completes normally with no prompt — the file is still saved to Resources, just not linked to the QMS register. You can still link it manually via Supabase Table Editor if needed.

🔢How version detection works

The system reads the PDF content and looks for version numbers near keywords like Version History, Revision History, or Amendment. It finds the highest version present and compares it to the register.

Version row colour	What it means
Green ✅	Uploaded version is newer than the register — safe to link
Blue ℹ️	Same version as register — existing file link will be replaced
Amber ⚠️	Uploaded version appears older — double-check you have the right file
Grey ℹ️	Version could not be read from the PDF — verify manually

💡You can still click Link to QMS register even with an amber or grey warning — it is advisory only. Use your judgement based on the version history snippet shown.

✅What the QMS tracker does

The QMS tracker is your document management control centre. It does three things automatically:

1

Tracks every QMS document

Version number, status (Draft / Active / Under Review / Obsolete), issue date, annual review date, and who owns it.

2

Flags documents for annual review

Every time you open the QMS view, it checks all active documents. If any review date is within 60 days (or already past), it raises a flag automatically and shows it in the alert banner at the top.

3

Cascades change flags to related documents

When you mark a document as revised, the system checks which other documents depend on it and automatically flags them for review. For example, if you update the Quality Policy, the Quality Manual gets flagged because it references the policy.

✏️How to mark a document as revised

1

Click "Mark Revised" next to the document

Find the document in the QMS register table and click the Mark Revised button on the right.

2

Enter the new version number

Use 1.1 for minor changes (wording, formatting). Use 2.0 for major changes (process or scope changes).

3

Set the new review date

This defaults to one year from today. Adjust if needed.

4

Add a brief summary of what changed

This gets recorded in the flag message sent to downstream documents, so you know why they were flagged.

5

Click Confirm & Raise Flags

The document version updates, and any documents that depend on it are automatically flagged for review.

💡The panel shows you exactly which documents will be flagged before you confirm — so there are no surprises.

➕How to add a new document to the register

1

Click + Add Document

Top right of the Document Register section.

2

Enter the document number

Follow the numbering format: ATL-[CATEGORY]-[NNN]. For example: ATL-OPS-003. See the Document Numbering section of Help for the full category code list.

3

Fill in title, version, status, and dates

New documents start as Draft with version —. Once issued, change status to Active and set the review date to 12 months from the issue date.

4

Paste the file URL if you have it

Optional at this stage — you can add it later via Supabase.

⚠️Understanding flags and alerts

There are two types of flags. Both appear in the amber alert banner at the top of the QMS view, and the number shows on the QMS button in the nav bar.

📅

Annual review flag (blue)

Raised automatically when a document's review date is within 60 days, or already past. This is the system reminding you to check the document is still current and accurate. Once reviewed, click ✓ Acknowledge to clear the flag.

🔄

Change cascade flag (amber)

Raised when a document that yours depends on has been revised. For example, if the Document Control Procedure is updated, every document that references it gets a cascade flag. The flag message tells you exactly which document changed and what version it's now at.

🔴

Overdue review (red)

A review date that has already passed. Treat these urgently — an overdue review is a non-conformance under ISO 9001.

💡Acknowledging a flag doesn't mean you've reviewed the document — it just clears the alert. Make sure you actually open the document and check it before acknowledging.

🔄What are dependencies?

A dependency means: "if Document A changes, Document B probably needs to be reviewed too." For example, the Quality Manual depends on the Quality Policy — if the policy changes, the manual may need updating to stay consistent.

Dependencies are shown in two ways:

1

The dependency diagram

An interactive map showing all documents as nodes. Arrows point from source to target (i.e. arrow means "affects"). Hover over any node to highlight just its connections. Drag nodes around to rearrange the layout. Colour-coded by document category.

2

The dependency list

A plain list of all source → target relationships with the reason recorded. You can delete any dependency using the ✕ button.

➕How to add a dependency

1

Click + Add Dependency

Top right of the Document Register section.

2

Select the source document

This is the document that, when changed, should trigger a review of other documents.

3

Select the target document

This is the document that needs reviewing if the source changes.

4

Write a brief reason

Explain why the relationship exists. This appears in the flag message so future-you knows what to check. Example: Quality Manual must reflect commitments stated in Quality Policy.

🏷️Document numbering system

All Atlam QMS documents follow this format: ATL-[CATEGORY]-[NNN]

For example: ATL-QMS-001 = Atlam, Quality Management System category, first document.

Code	Category	What goes here
QMS	Quality Management System	Quality manual, quality policy, QMS procedures
WHS	Work Health & Safety	WHS policy, SWMS, incident forms, hazard registers
OPS	Operations	Service SOPs, work instructions, job forms, calibration procedures
AST	Asset Management	Asset register, asset management procedure
CTR	Contracts & Commercial	Contract templates, contract register
HR	Human Resources	Training records, competency assessments, induction
IT	Information Technology	Software development procedures (future)
EXT	External Documents	Referenced standards and legislation (listed, not uploaded)

💡Numbers are sequential within each category. The next QMS document is ATL-QMS-005, the next OPS document is ATL-OPS-003, and so on. Check the Document Register to see what's already been used.

📋Current document plan

Doc No.	Title	Status
ATL-QMS-001	Document Control Procedure	Active
ATL-QMS-002	Quality Policy	Active
ATL-QMS-003	Quality Manual	Draft
ATL-QMS-004	Quality Objectives Register	Draft
ATL-WHS-001	Work Health & Safety Policy	Draft
ATL-OPS-001	Service & Repair SOP	Draft
ATL-OPS-002	Calibration & Test Equipment Procedure	Draft
ATL-AST-001	Asset Management Procedure	Draft
ATL-CTR-001	Contract Management Procedure	Draft

🗄️About Supabase

Supabase is the database and file storage service that powers this intranet. You don't need to go there for day-to-day use, but occasionally you'll need it for setup tasks.

✓

How to access Supabase

Go to supabase.com → Sign in → Open your project. The project URL is sgjaxhrbndcdgebnlrcb.supabase.co.

1

Table Editor

Where you can view and edit data in your tables. Useful for manually editing records or correcting data. QMS file linking now happens automatically from within the intranet — you rarely need to edit qms_documents here directly.

2

Storage

Where your uploaded files live, inside a bucket called intranet-files. You can browse, download, or delete files here.

3

SQL Editor

Where you run SQL scripts like the QMS migration. Only needed for setup or advanced changes.

💡You're on the Supabase free tier. It includes 500MB database storage and 1GB file storage. Upgrade to Pro ($25/month) when the business generates revenue if you need more.

⚙️How the intranet is deployed

Understanding this helps you update the intranet in future:

1

Edit index.html on your computer

The entire intranet is one HTML file. Edit it locally.

2

Commit and push to GitHub

Push to the Atlam-Intranet private repo at github.com/Peter-Sciberras/Atlam-Intranet.

3

Cloudflare deploys automatically

Within 30–60 seconds, Cloudflare runs build.sh which injects your Supabase credentials and deploys the updated file to atlam-intranet.pages.dev.

💡Never hardcode your Supabase URL or key directly in index.html — they're stored safely in Cloudflare's environment variables and injected at build time.

Good , team.

Upload Resource

Add Category

Delete Resource