Skip to guide content
WavelinkWAVELINKAJ OFFSHORE SOLUTIONS · HELP
Help centreAdministration & documents

CORE GUIDE TOPIC · companybranding

About these instructions

This reader standardises presentation, not the entire procedure library. The original instructions, version labels and warnings are retained. Some topics describe the local Windows hub or earlier interface labels. They must not be read as proof that all desktop setup, imports or recovery work is available in the hosted browser.

The full wording, hosted/local scope, native Help and PDF review remains on the development list. Use only company-approved operational procedures; viewing Help does not approve a checklist, release equipment or verify work.

On this page 24 sections
  1. Your company. Your reports.
  2. One profile in each project
  3. Separate customer and software identities
  4. Start deliberately
  5. What you can set
  6. No change to saved evidence
  7. Set up and preview your identity
  8. Upload a real company logo
  9. Preview before saving
  10. Confirm one project-wide change
  11. Remove or disable without deleting records
  12. Conflicts and interrupted saves
  13. Reuse profiles without changing records
  14. Export a reusable profile
  15. Import into another project
  16. Keep project backups
  17. Work in one authorised account
  18. Practise with fictional examples
  19. Know the output boundaries
  20. Generated PDF coverage
  21. Kept outside this first increment
  22. Keep records recognisable
  23. Language and document security
  24. Update safely

User guide / Administration | Access and sensitive exports

Company branding & reports

Wavelink 1.34.10 | AJ Offshore Solutions

Your company. Your reports.

Wavelink 1.34.10 / Company branding & reports

One profile in each project

In the browser, open Administration > Company branding. In desktop Admin, choose Company branding in the existing sidebar. A current named project administrator is required. Each project has its own saved company identity.

Separate customer and software identities

The company logo, company name and chosen header/footer identify the report owner. Wavelink remains the software identity in a small generation marker. The app interface, sign-in screen, installer and publisher details are not rebranded.

Start deliberately

Existing projects retain their default appearance until an administrator enables company branding. Choose Edit company branding, enter the company name and select the generated PDF report types that should use it.

What you can set

Company name; company address on an optional cover; company email, phone and website; header/strapline; footer note; classification wording; report accent colour; left/right logo position; and an optional cover page. The accent decorates the report frame; safety/status colours in the data remain unchanged.

No change to saved evidence

Branding is applied at export time. It does not change the saved checklist, task, fault, signature, approval, reading, original document or record number. A newly exported report may therefore use a newer company profile than an earlier downloaded copy.

Set up and preview your identity

Choose logo > edit company details > preview > confirm and save

Upload a real company logo

Choose one PNG or JPEG up to 2 MB, 4096 pixels per side and 8 million pixels. Wavelink decodes and normalises it, strips image metadata, and preserves its aspect ratio. Transparent PNG is suitable. SVG, animation, external image URLs and arbitrary file paths are not accepted.

Preview before saving

Download unsaved PDF preview in the browser, or Preview PDF in desktop Admin, generates fictional sample content with a continuation page. An enabled cover setting adds a cover. This does not create a checklist or task, save the logo/profile or publish any operational record.

Confirm one project-wide change

Supply a reason, review the report-type selection, tick the confirmation and choose Save company profile. The saved profile has a revision, author and UTC time. Recent changes are shown in the workspace. Changes are checked again against your current authority.

Remove or disable without deleting records

Remove the logo from the draft and save to use text-only branding. Disable company branding and save to return future PDFs to their default appearance. Deselecting one report type leaves that type on its original layout. No existing exported PDF is edited or deleted.

Conflicts and interrupted saves

When another administrator saves first, reload and review rather than overwriting their profile. A retry of an unchanged save uses the same operation reference. After an uncertain save, retry unchanged or export the draft before discarding and reloading. Never assume a timeout means nothing was saved.

Reuse profiles without changing records

Portable company settings, not a project-data import

Export a reusable profile

Export saved profile creates a .ajbrand file containing company settings and the normalised logo. It does not contain user accounts, passwords, tasks, signatures or the profile audit history. Export draft retains an unsaved proposal instead; it is not proof of a saved change.

Import into another project

Open Company branding in the destination project and choose Import company profile. The file is validated and staged as an unsaved draft. Inspect the destination, company details, classification wording and report types. Preview and save explicitly. It does not automatically overwrite the saved profile.

Keep project backups

Full-project backups and full-project transfers include the saved company profile and its change history. Selected workspace/template transfers do not silently import branding; use .ajbrand for that purpose. Protect profiles because company contact information and the logo are included.

Work in one authorised account

Browser edits are held only in the current page memory. Same-account re-entry can resume wording after expiry; a different account cannot take it over. Closing/reloading can lose unsaved work. Desktop edits stay in the current application session. Neither interface adds an automatic offline save queue.

Practise with fictional examples

The example folder 15_Company_Branding includes enabled demo profiles, a disabled blank starter and a sample preview. Use them in an isolated training project; replace all fictional identity details before producing company deliverables. Importing a profile never certifies the company or a logo licence.

Know the output boundaries

Branding is presentation, not evidence editing or access control

Generated PDF coverage

Selected checklist records, inventory-verification reports, Tasks, maintenance work orders, certificate-register records, toolbox talks, published handovers, Fault Reports, shipment manifests and operations-log PDFs use the common company envelope. Continuation pages repeat the company header/footer.

Kept outside this first increment

Raw Excel/CSV/JSON data, original uploaded files, reusable checklist definitions, backup/transfer formats, QR labels and software documentation are unchanged. The company address appears on the optional cover. This is not a drag-and-drop report designer or arbitrary per-template layout editor.

Keep records recognisable

Mandatory statuses, warnings, saved authors, approvals and results are not configurable branding fields. Table semantics and safety/status colours stay intact. Wavelink generation details, company-profile revision and page numbers remain on branded outputs. No signature is fabricated by a logo or footer.

Language and document security

Company text currently uses Western European characters supported by the built-in report font. Other scripts can appear in the uploaded logo; broader multilingual fonts are pending. A confidentiality label is printed wording, not encryption or recipient enforcement. Existing source permissions still control export.

Update safely

Back up the project, preserve unsent work in every browser/window, stop the hub and close Admin. Update in place without uninstalling or clearing storage. Use 1.34.10+ on the machine generating branded reports. The unsigned online installer is not a Windows acceptance test; verify installation and representative company outputs before operational deployment.