# Admin Console

{% hint style="info" %}
If you're a team member you probably won't be spending much time here. Check out the [Extension Console](/platform-overview/extension-console.md) instead.
{% endhint %}

You might have noticed as you completed activation and account signup that you found yourself in a portal that looked a bit like this.

<figure><img src="/files/cZ5BTbnlaSueqEdcb4ra" alt=""><figcaption></figcaption></figure>

This is the Admin Console and you can think of it as your home for setting up anything with your team for PixieBrix.&#x20;

### What is the Admin Console?

The Admin Console is a web app for creating and managing PixieBrix teams, viewing user telemetry, troubleshooting errors, and more. You can access the Admin Console at <https://app.pixiebrix.com/>.

The Admin Console has multiple sections, some of which may be hidden depending on your role.&#x20;

### 📖 Campaigns

A Campaign is a reporting entity to track engagement for a set of team members.

* [**🌐 Click here to learn how to create a Campaign**](/platform-overview/admin-console/campaigns.md)

### 👩‍💻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.

* [**🌐 Click here to learn more about Groups**](/managing-teams/access-control/groups.md)

### 📤 Deployments

Deployments enable an Admin to automatically provision PixieBrix mods to groups of team members.

* [**🌐 Click here to learn more about Deployments**](/deploying-mods.md)

### 💽 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.\*\*\*\*

* [**🌐 Click here to learn more about 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.

* [**🌐 Click here to learn more about how to use Service Accounts**](/developer-api/service-accounts.md)

### 📈 **Telemetry**

Telemetry provides engagement and errors information to help you detect, diagnose, and debug problems with mods.

If you want to enable email notifications when a new member joins your team or when a new error occurs in a deployment, click the **Contacts** tab and specify a new contact:&#x20;

<figure><img src="/files/H1BVTjqB9iDXw22Its3n" alt=""><figcaption></figcaption></figure>

At the bottom of the Admin Console you’ll find your teams’ **Settings**, which enable an Admin to configure:

* Your team’s **name**
* Your team’s **scope** (the identifier after the @ sign that provides a unique namespace for brick and mods your team creates)
* Your team’s **default** role: the role automatically assigned to any new team member associated via email domain or Group membership (Enterprise-only)

Learn more about [Telemetry](/platform-overview/admin-console/telemetry.md).


---

# Agent Instructions: 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:

```
GET https://docs.pixiebrix.com/platform-overview/admin-console.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.