> For the complete documentation index, see [llms.txt](https://docs.betterbuilding.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.betterbuilding.io/create-your-first-project/create-a-team.md). # Create a Team Teams are the central hub for all your Projects, providing a unified space for efficient project management and also act as a cost centre. As the Team Owner, you’re the super admin, fully in control of team settings, permissions, and collaboration. You manage members, projects, and access across your entire Team workspace. If a Team already exists within your office or organisation, locate the creator, they can add you as a Team Member for shared access and collaboration. **Team Owner -** When you create a Team, you become the Team Owner by default. As the Owner, you can invite Team Members to collaborate on Projects within that Team. **Team Member -** Invite Team Members to collaborate on Projects and Designs, reviewing, editing, and saving changes across the Team. The key distinction: Team Owners hold administrative privileges, Members do not. **Team Guest -** Invite Guests to your Invite Guests to specific Projects for design review and collaboration. Guests have view-only access, they cannot access your Team or other Projects, nor can they save changes to any Design. ## Create A Team To create a Team, start by assigning a Team 'Name', this is usually the name of your company or organisation. Avoid using Project names or individual names, as this can lead to confusion and limit scalability as your use of Better Building grows. Before setting up a new Team, it's important to check whether someone in your office, or perhaps in another regional location, is already using Better Building under an existing Plan. If they are, ask to be invited to join their Plan as a Team Member instead. This ensures everything stays connected and avoids creating duplicate Teams. --- # 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.betterbuilding.io/create-your-first-project/create-a-team.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.