> For the complete documentation index, see [llms.txt](https://docs.unibright.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unibright.one/getting-started/workgroups.md).
# Workgroups
On the workgroups page you can create and manage workgroups, invite other participants to your workgroup and see your invitations into other workgroups.
Workgroups are groups of participants that exchange business data within a workflow.
Under Create New Workgroup, you can create a new workgroup with a describing identifier.
After the creation you can manage...
* the number of needed approvals per workgroup for a workflow to be considered complete
* the information if a complete workflow should be directly exited into a single transaction on the blockchain
* the information if a veto is active, where a veto means a workflow with one ore more negative feedbacks (='rejection(s)') will not be exited
* the participants of the workgroup by inviting them via email (you have to use the email addresses that the participants are registered with at Unibright ONE)
If somebody else invitied you to their workgroup, you see the pending invitiations which you can accept or reject. Your existing workgropups are listed below.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.unibright.one/getting-started/workgroups.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.