> ## Documentation Index > Fetch the complete documentation index at: https://docs.aiola.app/llms.txt > Use this file to discover all available pages before exploring further. # Central and Workspaces > Understand which Aiola surfaces operate on one repository workspace, aggregate multiple workspaces, or configure the entire app. Use a workspace when the action belongs to one repository; use Central when you need a cross-workspace view or an app-wide setting. A Central route is not automatically an aggregate—the matrix below identifies the actual behavior. ## Mental model | Scope | Context | Data and actions | | ---------------------- | --------------------------------- | ---------------------------------------------------------------------------------------- | | Workspace | One selected local repository | Repository files, project settings, project records, and work executed in that workspace | | Central aggregate | All eligible workspaces | Combines workspace-tagged records and sends actions back to the owning workspace | | Central shared surface | App-wide or synthetic context | Reuses a component or manages state that does not belong to one repository | | Central settings | Signed-in account and desktop app | Account, UI, providers, phone connections, hosted MCP, and usage | ## Route matrix | Feature | Workspace page | Central page | Both | Central behavior | | ----------- | ------------------------------------------ | -------------------- | ---- | ---------------------------------------------------------------------- | | Home | `/home` | `/central/home` | Yes | True aggregate plus a workspace-targeted chat composer | | Tasks | `/tasks` | `/central/tasks` | Yes | True aggregate; task IDs are mapped back to their workspace | | GitHub | `/github` | `/central/github` | Yes | True aggregate of issues and pull requests fetched per workspace | | App Logs | `/app-logs` | `/central/app-logs` | Yes | True aggregate of project-tagged log groups | | Feedback | `/feedback` | `/central/feedback` | Yes | True aggregate with per-project field schemas and context | | Analytics | `/analytics` | `/central/analytics` | Yes | True aggregate of site results, with the uniqueness caveat below | | Calendar | `/calendar` | `/central/calendar` | Yes | True aggregate of scheduled tasks and automations | | Notebook | `/plan`, with `/notes` and `/todo` aliases | — | No | Workspace only | | Automations | `/automations` | — | No | Editing is workspace only; Central Home and Calendar can show activity | | Agents | `/agents` | — | No | Workspace only | | Project | `/info` | — | No | Workspace only | | Skills | `/skills` | `/central/skills` | Yes | Same page component; scope depends on selected workspace context | | Terminals | `/terminals` | `/central/terminals` | Yes | Separate terminal canvas using workspace ID `__central__` | The default workspace sidebar lists Home, Tasks, GitHub, App Logs, Feedback, Analytics, Calendar, Notebook, Automations, Agents, and Project. The default Central sidebar lists Home, Tasks, App Logs, Feedback, Analytics, Calendar, GitHub, and Skills. Central Terminals is opened from the Central terminal control rather than the editable Central navigation list. ## True aggregate twins Central Home, Tasks, App Logs, Feedback, Analytics, Calendar, and GitHub combine data from multiple workspaces. Their records retain workspace or project context so opening, editing, executing, or triaging a record targets its owner. | Feature | Aggregate rule that matters | | --------- | -------------------------------------------------------------------------------------------------------------------------------- | | Home | Combines task, log, feedback, GitHub, automation, calendar, and notification summaries; its composer requires a target workspace | | Tasks | Loads all workspace task files; composite mappings prevent equal local task IDs from colliding | | App Logs | Loads central log groups and preserves project filtering and per-project caches | | Feedback | Loads all feedback plus field definitions keyed by project name | | Analytics | Fetches each visible analytics site and adds the site summaries | | Calendar | Combines scheduled tasks and recurring automation occurrences, using the app-wide timezone | | GitHub | Fetches each workspace separately, attaches workspace ID/name, then combines Issues and Pull Requests | Central Analytics adds each site's `visitors` value. It does not deduplicate the same person across sites, so its visitor total is the sum of per-site unique visitors rather than an account-wide unique-person count. ## Same-component twins Central Skills directly re-exports the workspace Skills page. It is a shared implementation, not a precomputed cross-workspace feed. Workspace-local skill discovery depends on workspace context, and starting a chat requires a workspace target. Central Terminals is also not an aggregate. It owns an independent terminal canvas under the synthetic workspace ID `__central__` and exposes only **Split** and **Canvas** as its top-level modes. ## Central-only settings Open **Central Settings** for app-wide configuration. These destinations have no per-workspace equivalent: | Group | Pages | | ----------- | ----------------------------- | | Account | General, Appearance, Keybinds | | Connections | Providers, Connections, MCP | | Billing | Usage | See [Central Settings](/core-features/central-settings) for every control. ## Workspace-only surfaces Notebook, Automations, Agents, and Project exist only in a selected workspace. Their settings and files belong to that repository context. Workspace settings also own repository defaults, instructions, Git behavior, task execution defaults, environment files and actions, project credentials, integrations, local MCP servers, monitor setup, and archived threads. See [Workspace Settings](/core-features/workspace-settings) for the complete settings order. ## Switching and context Selecting a workspace changes the repository path, project name, files, agents, branches, tasks, and project-backed monitor records used by workspace pages. A Central record retains its owner; actions resolve that owner before operating. Central Home is the exception that can become the normal Dashboard inline. Selecting a thread or entering draft mode mounts the Dashboard, and the Central composer persists its chosen target workspace. ## GUI Lifetime gating GUI Lifetime removes hosted monitoring surfaces while retaining local workspace functionality. | Area | Hidden or unavailable | | ----------------------------- | ----------------------------------------------------------------------------- | | Workspace navigation | App Logs, Feedback, Analytics | | Central navigation | App Logs, Feedback, Analytics | | Workspace settings navigation | API Key, App Logs, Analytics, Integrations | | Gated direct settings route | Feedback | | Central Home | Hosted App Logs, Feedback, and Analytics cards/data | | Hosted MCP | Hosted connector access; the local per-workspace MCP server continues to work | | Usage | Analytics usage; CLI-provider usage remains | Tasks, GitHub, Calendar, Automations, Agents, Notebook, Project, local terminals, local MCP servers, Providers, Connections, Appearance, and Keybinds remain local/app functionality.