Good , team.
Everything you need, in one place.
This is Atlam's internal hub. It has two main areas:
qms_migration.sql file. This creates the QMS tables and seeds your initial documents.file_url column. Repeat for each document.ATL-QMS-001 — Document Control Procedure), a short description, and choose a category.External URL: paste a link to a file already hosted somewhere (e.g. Google Drive, SharePoint).
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 |
+ Add category button on the Resources view. Consider adding a dedicated QMS Documents category to keep policy files separate.The QMS tracker and the file library are separate. Uploading a file to Resources doesn't automatically connect it to the QMS register — you need to paste the file's URL into the register manually. Here's how:
supabase.com → sign in → open your Atlam project (sgjaxhrbndcdgebnlrcb).file_url column. Click the cell and paste the URL. Press Enter or click Save.The QMS tracker is your document management control centre. It does three things automatically:
1.1 for minor changes (wording, formatting). Use 2.0 for major changes (process or scope changes).ATL-[CATEGORY]-[NNN]. For example: ATL-OPS-003. See the Document Numbering section of Help for the full category code list.—. Once issued, change status to Active and set the review date to 12 months from the issue date.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.
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:
Quality Manual must reflect commitments stated in Quality Policy.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) |
| 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 |
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.
supabase.com → Sign in → Open your project. The project URL is sgjaxhrbndcdgebnlrcb.supabase.co.qms_documents table, or to manually edit any record.intranet-files. You can browse, download, or delete files here.Understanding this helps you update the intranet in future:
Atlam-Intranet private repo at github.com/Peter-Sciberras/Atlam-Intranet.build.sh which injects your Supabase credentials and deploys the updated file to atlam-intranet.pages.dev.