> For the complete documentation index, see [llms.txt](https://docs.bugbug.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugbug.io/collaboration.md). # Collaboration - [Organizations](https://docs.bugbug.io/collaboration/organization-settings.md): Discover BugBug's collaboration and organization settings. You can modify, add or delete information regarding your organization. Optimize teamwork and enhance your productivity. - [Inviting team members](https://docs.bugbug.io/collaboration/inviting-team-members.md): Learn how to invite team members and enhance your team collaboration with BugBug. You can work together on test cases, share links to test results, empower developers and many more. - [Project access management](https://docs.bugbug.io/collaboration/project-access-management.md) - [Alerts](https://docs.bugbug.io/collaboration/alerts.md): Stay connected and informed with BugBug's collaboration notifications feature. Streamline teamwork and never miss your test results. Try it now for free! - [Sending email notification](https://docs.bugbug.io/collaboration/alerts/sending-email-notification.md) - [Sending webhook](https://docs.bugbug.io/collaboration/alerts/sending-webhook.md) - [Sending Slack message](https://docs.bugbug.io/collaboration/alerts/sending-slack-message.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://docs.bugbug.io/collaboration.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.