We use cookies to improve your experience and for marketing. Read our cookie policy & privacy policy.

Getting started · Console & account

Console Settings overview

StackUp TeamUpdated July 20264 min read

The Settings page is the home of your account context and platform configuration. It shows who you are, what plan you are on, which APIs are active, and gives you one-click access to every administrative area of the console: API keys, usage, team, domains, and subaccounts.

The Settings page

Open Settings from the console navigation. The page is organized into three layers: your account identity at the top, quick management cards in the middle, and subaccount management at the bottom. Everything administrative starts here.

Account details

The Account card describes your current authenticated workspace:

FieldWhat it is
Account nameThe workspace you are operating in, typically your publisher or company name.
EmailThe email of the signed-in user.
Account IDA unique identifier for the workspace. Use it when contacting support or referencing the account in integrations.
Your roleYour permission level in this workspace, for example Admin or Super Admin. Your role determines which settings you can change.
PlanYour current plan, for example Free Trial or Premium. See Usage & Plan for limits and consumption.

Active APIs and Data API keys

The Active APIs card shows the enrichment API keys currently active for V1 data access, so you can see at a glance whether programmatic access to your enrichment data is in use.

To create or revoke keys, open Data API Keys › Manage API Keys. Keys are Bearer tokens that grant access to the enrichment endpoints /v1/enrich and /v1/enrich/batch.

⚠
Treat API keys as secrets. Revoke any key you no longer use, and rotate keys if you suspect one has been exposed.

Quick management cards

Four cards link to the main administrative areas:

  • Data API Keys — create and revoke Bearer keys for enrichment API access.
  • Usage & Plan — review plan limits, monthly scans, and enabled capabilities. Covered in Usage & Plan.
  • Team — admins can invite teammates, update roles, and deactivate users. Covered in User management.
  • Domains — manage publisher domains used for curation and SDK attribution. Covered in Manage domains.

Subaccounts

Subaccounts are child accounts under your company, useful when you operate multiple publishers or want to separate clients from each other. Each subaccount has its own name and domain, and domains can be assigned to it directly (see Manage domains).

To create one, enter a name and domain in the Subaccounts section and click Create. Existing subaccounts appear in the table below with their status and actions.

💡
Tip: use subaccounts when data access needs to be separated, for example one subaccount per publisher client. Domains assigned to a subaccount keep that client's data scoped to it.

Was this article helpful?