> For the complete documentation index, see [llms.txt](https://docs.gospace.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gospace.com/user-app/auto-allocate.md). # Auto-allocate ## Auto Allocate Learn how gospace's auto-allocate feature automatically assigns team zones without requiring manual scheduling ### Overview Auto-allocate removes the need for scheduling entirely by automatically assigning team zones based on attendance forecasts. Teams receive notifications when their zones change. ### Allocation Types #### By Space Teams are allocated their own dynamic neighborhood: * Teams get dedicated spaces within the office * Individual members without teams receive specific spaces * Space size adjusts based on attendance forecasts #### By Zone Teams are allocated to configurable zones on the floorplan: * Teams see their designated zone in notifications * Members can self-organize within their zone * Zones are configured through the admin console ### Forecast Options #### Daily Aggregate Forecasts How it works: * Teams receive allocations based on daily forecasted attendance * Zone sizes adjust daily based on team forecasts * 97% forecast accuracy for team attendance * Consistent Monday-to-Monday allocation patterns #### Weekly Peak Forecasts How it works: * Teams receive fixed zone sizes based on peak attendance * Zones remain consistent throughout the week * Size determined by highest expected attendance **Important:** Auto-allocate cannot be used simultaneously with manual or auto-scheduling features as this involves no human scheduling at all. ### User Experience With auto-allocate enabled: * No manual booking * Automatic notifications when team zones change * View allocated zones in the user app * Teams stay together in their designated dynamic areas --- # 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.gospace.com/user-app/auto-allocate.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.