Skip to main content
Knowledge Library

GDM Docs

A central home for product guides, feature references, scenarios, tips, licensing notes, and support knowledge.

Start Here

Find The Right Guide

This library is designed to grow with the website. Each product section should explain what the feature does, when to use it, what to check before relying on it, and practical scenarios that make the guidance easy to apply.

Dar Payroll

Complete guide to the payroll workspace: employees, payslips, FS5, leave, HR records, reports, backups, and common operating scenarios.

Open guide

Licensing

How license-gated products are requested, validated, stored locally, and supported while payment automation is still being developed.

Read notes

Support

How visitors, customers, and product users should ask questions, report issues, request access, and send product feedback.

View support path

Website

Reference map for the public website: products, projects, blog, contact flow, client portal, privacy pages, and account entry points.

Browse map

Policies

Quick links and plain-language notes for privacy, terms, local storage, account sessions, and responsible use of product data.

Review policy notes

Future Products

Reserved space for the next product guides. New sections should follow the same feature, tips, scenarios, and troubleshooting format.

Template ready
Library Standard

What Each Guide Should Contain

Good documentation is more than a feature list. Every product page should teach the workflow, call out risks, and give enough examples that a real user can finish the job without guessing.

Feature reference

What the screen or tool does, what inputs it needs, and what output it creates.

Helpful tips

Small habits that prevent mistakes, save time, or make records easier to audit later.

Scenarios

Realistic examples such as onboarding, monthly payroll, overtime, terminations, or support handover.

Responsibility notes

Clear boundaries around local data, backups, legal review, licensing, and customer responsibility.

Licensing Notes

Licensed products use a customer access flow instead of open public access. Dar Payroll currently supports a manual license request path from the product page and documentation, with license validation handled by the site API.

Request pathCustomers use the product or documentation call-to-action to request access through the contact page.
ValidationThe product validates license details before loading the payroll workspace.
Local storageLicense email, license key, and a random browser device ID can be stored locally so repeat access is smoother.
License authorityProducts validate existing licenses only. All license creation stays inside the protected License Admin Panel.

Support Path

For public users, the contact page is the main support entry point. For product users, the documentation comments and product-specific contact links create a cleaner path for questions, feature requests, and license issues.

  1. Use the relevant product documentation page first, especially for workflow or feature questions.
  2. Use the comments panel on documentation pages for public clarifications and product improvement notes.
  3. Use the contact form for account, license, billing, access, or private data questions.
  4. Include product name, browser, relevant period or screen, and what was expected versus what happened.

Website Map

The public site separates portfolio content from product and customer-facing functions. The docs library is the bridge between the marketing pages and the operational tools.

ProductsCommercial software catalogue, beginning with Dar Payroll.
ProjectsPortfolio examples and technical work samples.
BlogArticles, release notes, and longer-form technical writing.
Client portalAuthenticated area for customer-facing access and future account features.

Policy And Data Notes

The documentation should keep the trust model visible. Public pages use essential storage only; account and product pages may use additional browser storage when needed for their local features.

Privacy Terms Local storage License checks Backups
For payroll and employment records, users should keep their own backups and review official submissions with the right advisor or authority. Documentation can explain the product, but it should not replace professional judgement.

Next Additions

The next best improvement is to split larger guides into smaller linked articles once there is enough content. Dar Payroll can eventually become a mini-manual with separate pages for payslips, FS5, leave, backups, and troubleshooting.