> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/platform-overview/admin-console.md). # Admin Console ### What is the Admin Console? The Admin Console is web-based Control Plane for creating and managing PixieBrix teams, configuring policies, assigning policies and automations, and more. You can access the Admin Console at . The Admin Console has multiple screens, some of which may be hidden depending on your role and your team subscription.
### πŸ‘©β€πŸ’»Groups Groups are sets of team members that have access (read or edit) to any number of bricks, databases, and shared Cloud Integration configurations. Additionally, an Admin can associate a Deployment with one or more Groups to have PixieBrix automatically deploy a Mod to those team members. Learn more about managing [Groups](/managing-teams/access-control/groups.md) ### πŸ“€ Deployments Mod Deployments enable an Admin to automatically provision PixieBrix mods to groups of team members. Mods are custom controls or automations. Learn more about [Deploying Mods](/deploying-mods.md) ### :judge: Policies Policies are security and compliance policies you can assign to groups of team members. For access to our detailed documentation on policies, contact , or your account manager. ### πŸ’½ Team Databases Team Databases enable a mod to store data across runs, installs, and team members. A Team Database is a key-value store. Each record is referenced by a unique key, and stores a JSON object. Learn more about [Storing Data with Team Databases](/storing-data-with-team-databases.md) ### πŸ€– **Service Accounts** Service Accounts are API-only accounts. Like their human counterparts, Service Accounts have a Role and can be added to a Group(s). Unlike human team members, Service Accounts do not count toward your Organization's subscription utilization. Learn more about [Service Accounts](/developer-api/service-accounts.md) ### :stopwatch: Member Activity The Member Activity screen displays member activity recorded by policies and/or custom logging deployed as mods. For access to our detailed documentation on member activity, contact , or your account manager. ### :shield: Security Events The Security Events screen displays security events reported by policies and/or custom controls deployed as mods. For access to our detailed documentation on security events, contact , or your account manager. ### πŸ“ˆ **Deployment Errors** The Deployment Errors screen helps you detect, diagnose, and debug problems with your deployed mods. Learn more about [Deployment Errors](/deploying-mods/telemetry.md) ### :gear: Settings The Settings screen enables an Admin to configure Team Settings: * General: Team Name, Default Role * Security: Session Timeouts, etc. * Artificial Intelligence (AI) Settings * Theme: Custom Branding --- # 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.pixiebrix.com/platform-overview/admin-console.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.