Console

Use the Platform Console to manage Applications, teammates, Console settings, and account access. End Users from your product do not log in to the Platform Console. They are mapped into an Application through your backend API calls.

What the Platform Console Is For

The Platform Console helps your team manage the operational side of the Editor plugin.

From the Console, Owners and Admins can:

Create and open Applications.
Invite teammates and manage roles.
Assign teammates to Applications.
Update Console-level company information.
Switch between accessible Consoles or product spaces.

Application-specific setup happens after you open an Application.

Console vs Application

The Platform Console and Application workspace serve different purposes.

Area	What it controls
Platform Console	Team access, teammates, Console settings, account access, and the list of Applications.
Application	API credentials, Push URL, Domain, Appearance, Editor Controls, End Users, credits, usage, and editor configuration.

Use the Platform Console when you are managing people, access, and high-level organization settings.

Use an Application when you are configuring a specific integration, product, customer, brand, or environment.

Main Console Pages

Page	Purpose
Applications	Create, open, rename, or delete Applications.
Teammates	Invite teammates, assign roles, and manage Application access.
Console Settings	Manage organization-level information for the Console.
Account & Access	Understand account switching, Console access, and invitation acceptance.

Switching Consoles and Applications

One Account can have access to multiple Platform Consoles or product spaces.

Use My Access or the account access menu when you need to:

Switch to another Platform Console.
Accept a pending invitation.
Move between accessible AuroraSendcloud product areas.
Confirm which Console you are currently managing.

Inside a Platform Console, use the Application list or Application switcher to move between Applications.

Teammates only see Applications assigned to them. Owners and Admins can access all Applications in the Console.

Typical Admin Workflow

A Console admin usually starts with this flow:

Sign up or log in.
Enter the correct Platform Console.
Create or open an Application.
Create API credentials inside the Application.
Invite teammates if more people need access.
Assign Application access to teammates.
Continue to the integration flow.

For the first setup path, see Sign Up and Create an Application.

Permissions at a Glance

Role	Console access	Application access
Owner	Full access. Owns the Console.	All Applications.
Admin	Can manage Console settings, teammates, and Applications.	All Applications.
Teammate	Limited Console access.	Only assigned Applications.

Use Teammates for detailed role and invitation behavior.

What Integrators Should Know

Most integration work is Application-level work, not Console-level work.

Your developers mainly need access to the Application where they will:

Create API credentials.
Configure Push URL.
Configure Domain if using a custom editor access domain.
Review End Users, credits, and usage.

The Platform Console is the entry point for finding or creating that Application and managing who can access it.