> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/complaints-management/access/configurator-onboarding-guide/setup-new-account.md). # Setup New Account ## Overview Make sure the following are taken into consideration before you begin setting up a new account. * Your account’s name and a short unique code you want to use (e.g., Nairobi under root ke or default) — this code is permanent and cannot be changed later, so pick it carefully. * A logo (if you have one) — optional, can be added later. * An idea of your administrative boundary structure (e.g. City → Ward → Locality). * A list of departments and job titles used in your organisation. ## Setup Onboarding happens in four phases. You must complete them in order → each phase unlocks the next: **Four Phases of Onboarding**


Phase 1	Setup Tenant & Branding	Create the account itself and upload the branding (logo, name) shown to citizens.
Phase 2	Setup Boundary	Define the geographic areas - your account is divided into (e.g. wards, zones) — either by uploading an Excel sheet, importing them from an existing hierarchy or fetching it from OpenStreetMap
Phase 3	Setup Common Masters	Set up departments, the types of complaints citizens can file, and how those complaint types are organised (hierarchy).
Phase 4	Onboard Employees	Add the staff who will actually resolve complaints, and assign them to departments and boundaries.

Once all four are done, you will land on a summary page confirming what was set up — and from then on you are in the Management Console. --- # 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://docs.digit.org/complaints-management/access/configurator-onboarding-guide/setup-new-account.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.