Organizations and Teams

​

How organizations work

Every GDELT Cloud account has a personal organization. You can also create or join company organizations. Each organization is a separate workspace with its own plan, billing state, members, API keys, Query Unit usage, Brief Unit usage, and feature access. An account can belong to multiple organizations, and those organizations can have different plans. For example, your personal organization can stay on a free or solo plan while your company organization runs on a team plan with shared API keys and pooled usage. New company organizations start on Free. Creating an organization does not copy or inherit the personal organization’s paid plan; upgrade the company organization when you want team members, organization API keys, higher pooled quotas, Alerts, Briefs, or MCP access for that workspace.

​

Settings and members

Use Account -> Organization to switch organizations, edit organization details, invite teammates, manage roles, and review organization usage. Organization roles:

​

Common scenarios

​

Create a company organization

1. Open Account -> Organization.
2. Use the organization switcher to create a new organization.
3. Enter the company name, slug, and optional company domain.
4. Switch to the new organization before configuring billing, members, or API keys.

​

Put a company organization on its own plan

1. Switch to the company organization.
2. Open Account -> Subscription.
3. Choose the plan for that organization.
4. Confirm that Billing for shows the company organization before changing plans.

Your personal organization keeps its own plan. Company organization billing does not overwrite your personal workspace.

​

Invite members

1. Switch to the organization.
2. Open Account -> Organization.
3. Invite teammates by email.
4. Assign roles based on who should manage billing, members, and keys.

If the organization plan does not include team features, the members panel shows an upgrade path instead of the invite form.

​

Manage API keys for an organization

1. Switch to the organization.
2. Open Settings -> API Keys.
3. Create, rotate, or revoke keys for that organization.
4. Use descriptive labels such as Production, ETL Worker, or Analyst Sandbox.

API keys are scoped to the organization that created them. A key created in a company organization consumes that company’s quota, not the creator’s personal organization quota.

​

View and export usage

Open Usage after switching to the organization. Owners and admins can export organization usage by feature, member, and API key. Usage is separated into product groups such as V2 API, MCP, Agent, Brief, Alerts, and Web App. Briefs consume Brief Units and do not consume Query Units. API and direct MCP calls consume Query Units from the active organization.

​

Large-company administration

For a larger company, create one company organization, put that organization on the correct plan, invite users with owner/admin/member roles, and label API keys by system or environment. Admins can then report usage at the organization, feature, member, and API-key level from the Usage page and CSV exports. Use labels consistently: This keeps billing, quota, security, and reporting clear without mixing company activity into anyone’s personal organization.