> For the complete documentation index, see [llms.txt](https://docs.bezier.octue.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bezier.octue.com/getting-started/understanding-your-personal-organisation.md). # Understanding your personal organisation A quick overview of your personal workspace. {% embed url="" %} ### Introduction Once logged in, you will be directed to your personal workspace or organisation.
This workspace is designed exclusively for your use. You will notice the organisation name displayed on the left-hand sidebar.
*Pro Tip: Your account name is suffixed with "Personal" for easy identification.* ### Quickly add power curves Click on the "Quick Create" button located at the top right to create a new Power Curve.
### Access pre-loaded power curves **Organisational power curves** The "Organizational Power Curves" are those that you own. You have the ability to edit and share these with your team members.
To open a Power Curve, simply click on it. To make changes, switch to edit mode once you’re in detail view. To return to the list of Power Curves, click on "Power Curves" in the left-hand sidebar. This action will automatically redirect you to the main dashboard. **External power curves** The next tab, "External Power Curves," contains resources shared with you by external parties.
You can view these external Power Curves in detail, but editing them is not possible. ## Summary With this understanding, you are now equipped to explore, view, and edit power curves within your personal workspace. Next, we will proceed to creating a new organisation. --- # 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.bezier.octue.com/getting-started/understanding-your-personal-organisation.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.