Account Overview & Settings

This guide covers account settings in three areas: your personal profile, organization settings (including users and API keys), and billing.

Top bar#

The top right of every page has a notification bell and your user avatar.

Notification bell#

Opens the Notifications panel. With nothing pending it shows "All caught up". Member Alerts you receive in-app (Circuit Breaker pauses, Account suspension, Payment declines, Number pool miss) appear here. Delivery channels are set per user in Profile > Notifications.

Global search (Cmd+K)#

Press Cmd+K (Mac) or Ctrl+K (Windows and Linux) to open global search. Placeholder: "Search by name, ID, or sub-ID". Scope tabs: All, Buyers, Vendors, Sources, Destinations and Campaigns, plus Calls and Bids when you search from Reports. On Reports, the + and block icons on a search result add it as an include or exclude filter.

Avatar menu#

Quick links include Profile, Users, Billing and Sign out. Users and Billing open the same pages as Organization > Users and Organization > Billing.

Profile (/profile)#

Two tabs: Account and Notifications.

Account tab#

Shows your name and email address.

Appearance:

• Theme: light or dark.

Notifications tab#

A table with one row per alert and two channel columns, EMAIL and IN-APP. There are no SMS, Slack or push channels.

To silence an alert, turn off both channels. If an alert never arrives, check Organization > Member Alerts first (which alerts Members receive), then your own channels here.

Organization#

Open the organization pages from the organization name at the bottom of the left sidebar, or go to /organization/settings. Left navigation:

• General: Settings, Member Alerts, API Keys
• Access: Users
• Billing: Overview, Payments, Invoices, Usage, Rates

API Keys#

• List columns: Name, Key, Role, Scope, Created.
• Create API Key opens a dialog with Name and Role (Admin or Member, default Admin).
• Admin keys show a warning: "Creating an API key with Admin privileges grants full access to your organization through the API. This key can perform all administrative actions. Only create Admin API keys when necessary. If you want a third party to be able to update Call conversions or other data, you should use a Postback instead." You must tick "I confirm the risks of creating an Admin API key".
• The API authenticates with the key as the apiKey query parameter.

Good practice: one key per integration, Member role unless Admin is required, delete keys that are no longer used or may be exposed, and give third parties a Postback rather than an API key.

Users (/users)#

Organization > Users (page "Manage Users").

• Columns: Name, Email, Role.
• Invite User: enter Email and choose Role (Admin or Member). The user receives an invitation email.
• Each row has an edit icon, which opens Edit User (name, email, role and permissions), and a three-dot menu with Delete.

Roles#

• To make a Member view-only, edit the user and choose the Read-only Permission Template, or set each area to View.
• To hide revenue, payout or conversion data from a Member, edit the user and use Financial Visibility (Revenue, Payout, Conversions). Hidden values are removed from reports, charts, exports and call details.
• There is no Manager role and no per-campaign access restriction for organization users.

Buyer and vendor users are not organization users. They are invited from Buyers or Vendors > Users (Manage Access) with report-access toggles such as Show Payouts, Show Revenue, Show Conversions, Call Exports and Access Recordings, plus Create Numbers & Manage Tags for vendor users.

Billing#

Organization > Billing, or Billing in the avatar menu.

Overview#

• Plan: the current plan, with Change plan.
• Balance, with Add funds. The Add Funds dialog offers $100, $200, $500 and $1000 presets and requires agreeing to the Terms of Service.
• Auto-recharge, with Settings (minimum balance that triggers a recharge, and the recharge amount).
• Payment method, with Add payment method. Card payments run through Stripe.
• Recent payments.

Payments, Invoices, Usage and Rates#

• Payments: transaction history with date, payment method, status and amount.
• Invoices: invoices can be viewed and paid here.
• Usage: a daily table of consumption by line item (local and toll-free numbers, local and toll-free voice, AI voice, recording, transcription, AI, enrichment) with a daily cost. Columns: Date, DID (L), DID (TF), Voice (L), Voice (TF), AI Voice, Recording, Transcription, Intelligence, Enrichment, Daily Cost.

Auto-recharge guidance#

1. Set the minimum balance to at least two days of typical spend.
2. Set the recharge amount to cover three to five days.
3. Review after the first week.

Example: about $20 per day of spend, minimum balance $40, recharge $100.

Failed payments#

• A declined card now shows a visible error when it is added.
• A Payment declines Member Alert fires when a charge fails.

Common issues#

Cannot see organization settings, billing or API keys. The user is probably a Member or view-only Member. An Admin must change the role.

Theme changes not showing. Refresh the browser; clear cache if it persists.

Card declined. The form now shows the decline. Check card details and bank restrictions, or try another method.

Auto-recharge did not run. Confirm auto-recharge is enabled, a default payment method exists, and the minimum balance is set.

MCP connector cannot read data. Check Enable MCP Access in Organization > Settings, and that the user signed in with the email that has CallGrid access.

Do it with AI#

Ask Griddy, Claude or ChatGPT. Try: "Where do I turn on Auto-recharge?" Claude and ChatGPT need the CallGrid connector turned on (setup guides for Claude and ChatGPT).

The connector is read only. It looks things up and reads your data. You make the changes in CallGrid.