Skip to main content
Enterprise — Organizations are provisioned for companies on an Enterprise agreement. Contact sales if your company needs multiple teams under a single contract and administrative layer.
An organization on Dune is an administrative and billing container for multiple teams. It suits enterprises that want several team workspaces while keeping one subscription, consolidated usage, and consistent security policies. Organizations are optional. Standalone teams (not linked to an organization) continue to work as described in Teams and Roles: they hold their own plan, usage, and security settings.

How organizations relate to teams

LayerWhat it ownsTypical responsibilities
OrganizationThe Enterprise subscription, organization-wide usage pool, invoices, and organization-level security policiesCompany administrators align billing, credit policy, and who may join
TeamQueries, dashboards, API keys, uploads, and team roles (admin, editor, viewer)Day-to-day analytics work and collaboration
Teams under an organization behave like other teams for content: creation, sharing, ownership transfer, and the context switcher work the same way. What differs is that billing, plan, and certain security controls live at the organization, not on each team.

Plans and usage

  • The organization carries the paid Enterprise subscription. Individual teams inside it do not have separate plans; they draw from the organization’s entitlements and usage pool.
  • Organization administrators can govern how usage is shared:
    • Organization extra credit limit — Optionally cap pay-as-you-go (extra) spend for the entire organization.
    • Team usage limits — Optionally set per-team credit caps so teams cannot consume the full pool without limits, while still respecting the organization’s overall allowance.
Exact limits and commercial terms are defined in your agreement with Dune.

Organization membership and roles

Users can be members of an organization with one of two roles:
  • Admin — May open organization settings and manage teams, people, plan, usage, security, and organization profile (where the product allows).
  • Member — May participate in teams according to team membership; they do not manage organization-level settings.
This is separate from team roles (admin, editor, viewer on a given team). A user can be an organization member and have different roles on different teams.

Opening organization settings

Organization settings are available only to users whose organization role is Admin.
  1. Open the global context switcher at the top of Dune.
  2. Find your organization in the list.
  3. Select the more options menu (three dots) next to the organization name.
  4. Choose the section you need — for example Teams, People, Usage, Plan, Security, or Profile.
The product opens the corresponding page under https://dune.com/settings/o/… (the exact path is assigned for your organization).

What each section covers

  • Teams — List teams in the organization, open Add team to create another team workspace, and manage team-level actions available from this view.
  • People — View organization members and, as an organization admin, assign Admin or Member at the organization level.
  • Usage — Monitor consumption for the organization, including breakdowns that help you understand usage across teams.
  • Plan — Subscription details, billing address and payment method where applicable, invoices, and the Enable limits controls (organization-wide extra credit cap and optional per-team usage limits).
  • Security — Organization-wide controls including Google SSO domain restriction, Okta SSO, optional Okta event hook configuration when Okta is enabled, and two-factor authentication requirements. These apply to how people join and authenticate under the organization’s policy.
  • Profile — Organization display name and profile image.

Teams under an organization

When a team belongs to an organization:
  • The Plan tab is not shown in that team’s settings — billing and plan changes are handled in organization settings → Plan.
  • Security & Privacy settings that are governed at the organization (SSO domains, Okta, mandatory two-factor) are locked at the team level; configure them under organization settings → Security. Team-level options that remain (such as default content privacy where applicable) still appear in the team’s Security tab.
For step-by-step SSO setup, see Google SSO domain restriction and Okta SSO setup. When your teams are under an organization, complete those steps in organization security settings unless your onboarding specifies otherwise.

Teams and Roles

Team workspaces, invites, and team roles

Enterprise plan

Enterprise capabilities and how to engage with Dune