Support

FairWork is operated by KS Engineering Studios from Australia. We mainly support teams and educators here. For product help, billing questions (where applicable), or privacy and legal questions, email us—we aim to reply within a few Australian business days.

Contact
info.ks.engineeringstudios@gmail.com

Include your account email (if different), a short description of the issue, and any error message or screenshot. Do not send passwords or secrets.

Frequently asked questions

  • Are Terms and Privacy written for Australia?

    Yes. FairWork is operated from Australia with Australian customers in mind. The Terms reference the Australian Consumer Law (ACL) and New South Wales courts. The Privacy Policy references the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs). They are still general templates—get legal review before relying on them for regulated or high-risk use.

  • I have a privacy complaint. What can I do?

    Email us first at the contact address on this page so we can investigate and respond. If you are not satisfied, you may contact the Office of the Australian Information Commissioner (OAIC) at https://www.oaic.gov.au/

  • How do I get started?

    Sign in from the home page, create a team, then create a project inside that team. Add tasks with effort points, use the board to track status, and try auto-allocate or rebalance suggestions when workload feels uneven.

  • Will FairWork email me when a task is due or overdue?

    Yes, when the deployed stack is configured: a scheduled Lambda uses Amazon SES to email the assignee. You get a notice when a task is due within the next 24 hours, and at most one overdue notice per task per UTC day until the task is done. You must be set as the task assignee, and your team member record needs an email (for example from accepting an email invite). The Plan tab is only a preview—the emails are sent from AWS, not from your laptop.

  • I see “API not configured” on the dashboard. What do I do?

    FairWork needs a deployed backend. Set NEXT_PUBLIC_API_BASE_URL in your environment (for example apps/web/.env.local) to your API base URL, restart the dev server, and sign in again if you get 401 errors after changing pools.

  • What is the difference between a team and a project?

    A team is your workspace boundary (members, billing context if enabled, and a list of projects). A project holds tasks, docs, meetings, and reports for one initiative. You can have multiple projects under one team.

  • Can I choose my own team or project ID in the URL?

    When creating a team or project, you can optionally set a short “link ID” (lowercase letters, numbers, hyphens). If you leave it blank, the system assigns a random id. Link IDs cannot be changed later without creating a new team or project.

  • What is the sample tour?

    The sample tour is a read-only team and project that demonstrates the product. Duplicate the sample project inside your team to get an editable copy you can practice on.

  • Who can see my tasks and documents?

    Members of the same team—and specifically people with access to the same project—can see project content according to how you use invites and team membership. Do not store highly sensitive secrets in tasks or docs unless your risk assessment allows it.

  • How do I export data?

    Use the reports or export features available in your project workspace where enabled (for example contribution CSV export). Availability depends on your deployment and permissions.

  • Sign-in fails or I get repeated 401 errors.

    Confirm your Cognito app client, issuer URL, and API authorizer are aligned with the environment variables in the web app. Clear cookies for the site, sign out fully, and sign in again. If the problem persists, email support with the approximate time and browser you used (no passwords).

For legal terms see Terms of Service. For data practices see Privacy Policy.