> For the complete documentation index, see [llms.txt](https://docs.kiloiot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiloiot.io/account/how-organizations-start.md). # How Organizations Start How a Kilo IoT organization starts: a default workspace created for each new user, or joining one by invitation. An **organization** is the shared Kilo workspace containing devices, dashboards, rules, and team permissions. Your personal account joins a workspace before you start configuring a deployment. If a new user has no organization, Kilo creates a default one and makes that user its owner. An invitation is the route for joining someone else's existing organization; accepting it adds membership rather than creating another workspace. There is no separate **Create Organization** button in the interface. ## Default Organization When a user first accesses the platform and does not yet belong to any organization, the system automatically creates one and assigns the user as its owner. The organization is named based on the user's profile: | Profile state | Organization name | | -------------------- | ------------------------------------------- | | First name available | **{FirstName}'s IoT** (e.g., "Maria's IoT") | | First name empty | **User's IoT** | | Profile unavailable | **Default IoT** | This happens transparently — the user lands in their new organization without any extra steps. From there, they can rename the organization in [Organization Settings](/account/organization-settings.md) and invite colleagues through [Inviting Users](/account/inviting-users.md). ## Joining an Existing Organization The second path into an organization is by invitation. A member of an existing organization who has permission to manage users sends an invitation to someone who already has a Kilo IoT platform account. The recipient receives an email with a link. When they click the link and the acceptance succeeds, they join the organization with the permissions the inviter assigned. For the full invitation workflow, see [Inviting Users](/account/inviting-users.md) and [Accepting Invitations](/account/accepting-invitations.md). ## After Joining What a user can do inside the organization depends on the permissions assigned at invitation time — or, for the owner of a default organization, on the automatic access that comes with ownership. Permissions can be adjusted later by anyone with user management access. See [Roles and Page Access](/account/roles-and-page-access.md) for how the permission model works. --- # 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.kiloiot.io/account/how-organizations-start.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.