Comment on page
You might have noticed as you completed activation and account signup that you found yourself in a portal that looked a bit like this.
This is the Admin Console and you can think of it as your home for setting up anything with your team for PixieBrix.
The Admin Console has multiple sections, some of which may be hidden depending on your role.
A Campaign is a reporting entity to track engagement for a set of team members.
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.
Deployments enable an Admin to automatically provision PixieBrix mods to groups of team members.
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.****
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.
Telemetry provides engagement and errors information to help you detect, diagnose, and debug problems with mods.
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)
Last modified 22d ago