# 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](https://docs.pixiebrix.com/platform-overview/extension-console "mention") 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="https://2274778196-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fq123bF1HPQPV35s5vHa1%2Fuploads%2FO6cl2b3ZWTPcMokY4Tmp%2FUntitled%20(32).png?alt=media&#x26;token=502c51a7-0f7b-4aae-87b7-f8fb1a327ad2" 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**](https://docs.pixiebrix.com/platform-overview/admin-console/campaigns)

### 👩‍💻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**](https://docs.pixiebrix.com/managing-teams/access-control/groups)

### 📤 Deployments

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

* [**🌐 Click here to learn more about Deployments**](https://docs.pixiebrix.com/deploying-mods)

### 💽 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**](https://docs.pixiebrix.com/storing-data-with-team-databases)

### 🤖 **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**](https://docs.pixiebrix.com/developer-api/service-accounts)

### 📈 **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="https://2274778196-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fq123bF1HPQPV35s5vHa1%2Fuploads%2FLE4ZRqtKlbPPpZky35rk%2Fimage.png?alt=media&#x26;token=ab10a925-718b-4cf0-a4c2-6b228c820324" 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](https://docs.pixiebrix.com/platform-overview/admin-console/telemetry "mention").