> ## Documentation Index > Fetch the complete documentation index at: https://help.pantaos.com/llms.txt > Use this file to discover all available pages before exploring further. # What is PANTA OS? > PANTA OS is a single workspace that brings chat, assistants, apps, library, and administration together for individuals and teams. ## What It Is PANTA OS brings your organization’s AI tools into one workspace. Chats, assistants, apps, shared knowledge, community, and admin tools all work together in one place, with one login and centralized governance. The left sidebar is the spine of the product. Every major section is one click away: Dashboard, Community, Inbox, History, Library, Assistants, Apps, Admin, and Settings. The top half of the sidebar is where most users spend their time, while Admin and Settings are used primarily by administrators. English Images Documentations ## Why It Matters Most teams run several AI tools side by side. Knowledge gets fragmented, usage is hard to govern, and quality varies between users. PANTA OS replaces that pattern with a single environment where: * Chat, assistants, and apps share the same context, the same models, and the same library. * An assistant or app built by one person can be reused by the whole team. * Administrators see usage, spend, and adoption in one place, and can set token limits per model and per cycle. * Data stays inside your workspace and inside your region. ## How To Use PANTA OS Sign in to your organization's PANTA OS instance. You land on the Dashboard. The Dashboard greets you by name and shows a central chat box plus a filterable grid of all assistants and apps available to you. Type a prompt to start an ad hoc chat, or pick a tile to open a specialized assistant or app. Use the left sidebar to navigate between Community, Inbox, History, Library, and the expandable Assistants and Apps sections. Each list expands to show your most relevant entries directly, so you can jump in without a second click. Admins manage users, teams, integrations, branding, and token limits within the Admin Panel. Every user can adjust their own profile and personal integrations under Settings. ## Key Areas Central chat box, tag filters, and a grid of assistants and apps. Tabs split the grid into All, Assistants, Workflows, Tools, and Favorites. The Create Assistant button opens the creation modal with two paths: AI Assistant Creation and Manual Assistant Creation. Free form conversation with a model of your choice. The model selector at the top of the chat offers Auto Mode plus the available frontier models. Each model has a short description so you can pick deliberately. Internal feed for platform updates and company news, with tabs for Latest, Pinned, Company, and Platform. Posts are created by admins through the Community Feed section and can be targeted to specific teams or to all users. Slide over panel that lists notifications grouped by date, for example completed workflow runs. Opens on top of the current screen so you can act on a notification without losing context. Your past conversations and workflow runs, with tabs for Assistants, Workflows, and Favorites. Each entry shows progress and a quick actions menu, paginated for longer histories. All your content in one place, split into Generated content and Uploaded content. The Projects section lets you group items into projects with New Project. Collapsible list in the sidebar. Expanding it surfaces your most relevant assistants for direct access, without a detour through the Dashboard. Collapsible list in the sidebar containing multi step processes. The naming is not yet fully consistent across the product: the sidebar calls this area Apps, the cards on the Dashboard call the same items Workflows. Both terms refer to the same concept. ## Administration The Admin Panel is opened from the bottom of the sidebar and is organized into seven tabs: Top workflows by usage, top assistants by token consumption, time to first value, and quick actions for user management and analytics export. Active users, pending invitations, and recently deleted users in separate tabs. Add users manually or via Bulk import from Excel. Restore deleted users within the retention window. Create and edit teams. Each team has its own General, Members, Assistants, and Account action sections, plus an optional team image. The standard set includes Microsoft 365, Google, Notion, GitHub, and Microsoft Teams etc. Connecting at the tenant level makes a connector available; users still authorize personally in Settings. Create and publish posts to the Community Feed. Each post has a title, a content type, a text body, and an audience selector that targets all users or specific teams. Edit organization name, subdomain, logo, and the three theme colors that drive the workspace branding. Plan budgets, overage limits, and per-model token limits are defined in euros per billing cycle. Toggle automatic fallback to a cheaper model when a model limit is reached. The cycle reset date is configurable. ## Personal Settings Under Settings, each user manages their own preferences across four tabs: General preferences for the personal workspace experience, including language (German or English) and dark mode. Profile details such as name, email, and role, managed by administrators. Personal authorization for the standard tool connectors. Independent from the tenant level integrations configured by admins. Personal customization options for the workspace experience. ## Tips and Best Practices * Start in the Dashboard rather than in chat. The grid shows you what your team has already built, and reuse is faster than starting from a blank prompt. * Use the tag filter on the Dashboard to narrow down a large set of assistants and apps. Tags are managed centrally through the Manage tags dialog. * Treat the History as your safety net. Long running app runs and past chats are searchable there, even after you close the original conversation. * For repeated multi step work, build an app instead of a chat. The same logic that works as a prompt today scales better as a structured app tomorrow. * Admins should set Token limits per model early. The automatic fallback to a cheaper model prevents surprises at the end of the billing cycle. PANTA OS uses two names for the same concept in different places: the sidebar entry is called Apps, the Dashboard cards are called Workflows. Treat them as identical. If you build one, it appears in both views. ## Help Center None at the product level. Both refer to the same multi step processes. The naming differs only between the sidebar (Apps) and the Dashboard cards (Workflows). The Library and History also use the term Workflows when grouping results. Five standard connectors: Microsoft 365 (email, calendar, SharePoint), Google (Gmail, Calendar), Notion (pages, workspaces), GitHub (issues, pull requests, repositories), and Microsoft Teams (channels, chats, messages). Additional integrations can be added on request through the PANTA OS team. Open the Dashboard and switch to the Assistants tab in the grid. Filter by tag if the list is long. Public assistants from your organization appear next to your private ones; private assistants are only visible to you. You’ll be notified in the workflow sidebar when the flow is complete. Depending on the workflow, outputs may appear in the Library or be delivered by email. Yes. Open the Library, select Generated Content or Uploaded Content, then use the Projects section with New Project to create a project and move items into it. Admins can set an organization-wide plan budget and optional overage limit, along with optional per-model spending limits in euros per billing cycle. When a model limit is reached, requests automatically route to a cheaper model if the toggle is enabled, or are blocked if no fallback is available. The current cycle is shown in Token limits. Deleted users move to the Recently Deleted tab in User management for a limited number of days. During that window, admins can restore the account. After the window closes, the account is removed permanently.