> For the complete documentation index, see [llms.txt](https://handbook.sixpivot.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.sixpivot.com.au/new-starters/getting-started.md). # Getting started Hooray you're here! Welcome and congratulations! 🎉 We're very excited for you and hope we can give you a great onboarding experience. ## Nice to knows * Pay: We pay salary fortnightly * Superannuation: We also pay super fortnightly ❤️ * Xero: When we get back your forms, you will receive a log-in to Xero Me. This is where you can view/download your pay slips and enter leave forms * You will receive a calendar invite to a few things; Sixers, Xmas shutdown dates, etc., but we'll chat about these during your induction😊 * You'll be receiving a welcome pack which contains your shirt and a few other fun things * A few days before you start, we will add you to our company Slack channel. You can accept the invitations earlier if you want to look around or the day you start * We will organise your laptop before you start, check out the details [here](/perks-and-benefits/laptop-allowance.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://handbook.sixpivot.com.au/new-starters/getting-started.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.