Manage your Astra enterprise

You can create multiple Astra organizations to separate resources, billing, projects, access, and more. Organizations are either standalone or part of an enterprise:

Standalone organizations

On the Free and Pay As You Go subscription plans, organizations have no relationship to each other, and they are managed independently.

Enterprise organizations

On the Enterprise subscription plan, you can use enterprise organization management to centrally manage multiple related organizations under one enterprise.

Your Astra account can belong to both types of organizations, and you can be both an Enterprise Administrator and an Organization Administrator.

What is enterprise organization management

Enterprise organization management is a centralized administration feature that allows you to manage multiple organizations under one enterprise.

Enterprise organization management is limited to specific administrative activities for the organizations within an enterprise:

At the enterprise scope, you can do the following

  • Change the enterprise display name.

  • Add organizations to the enterprise.

  • Manage enterprise users and roles.

  • Manage enterprise application tokens.

  • Get billing and usage reports for all organizations in your enterprise.

At the enterprise scope, you cannot do the following

  • Manage payment methods and subscription plans.

    While you can request usage reports at the enterprise level, you must manage payments at the organization level.

  • Directly interact with resources in organizations, such as databases. This interaction happens at the organization level only.

    Enterprise organization management separates organization and enterprise permissions so that you can grant the appropriate level of access to each user throughout your administrative hierarchy.

  • Manage organizations that are outside your enterprise, even if you are the Organization Administrator for that organization.

    Enterprise organization management strictly applies to the organizations attached to your enterprise. If you need to manage an organization that is outside your enterprise, you must switch to that organization.

Access enterprise settings

  1. In the Astra Portal header, click Settings.

  2. In the Settings navigation menu, click the name of the active organization, and then select your enterprise.

  3. In the Settings navigation menu, click the category of settings that you want to manage:

Get the enterprise ID

  1. In the Astra Portal header, click Settings.

  2. In the Settings navigation menu, click the name of the active organization, and then select your enterprise.

  3. On the General page, click Copy to copy the enterprise ID.

Change the enterprise name

  1. In the Astra Portal header, click Settings.

  2. In the Settings navigation menu, click the name of the active organization, and then select your enterprise.

  3. On the General page, click Edit to change the enterprise’s display name.

Change the enterprise email address

  1. In the Astra Portal header, click Settings.

  2. In the Settings navigation menu, click the name of the active organization, and then select your enterprise.

  3. On the General page, click Update email, enter the desired email address, and then click Update email.

    DataStax sends a verification email to the new email address. To confirm this change, you or another Enterprise Administrator must have access to the new email address.

  4. Follow the link in the verification email to finalize the change.

Manage enterprise application tokens

Use enterprise application tokens to authenticate DevOps API operations that require enterprise permissions.

For instructions and more information, see Manage application tokens.

Manage organizations in your enterprise

At the enterprise level, you can view, add, and remove organizations in your enterprise.

All other organization administration takes place at the organization level. For information about organization settings, see Manage Astra organizations.

View organizations in your enterprise

  1. In the Astra Portal header, click Settings.

  2. In the Settings navigation menu, click the name of the active organization or enterprise, and then select your enterprise.

  3. In the Settings navigation menu, click Overview to view a list of all organizations in your enterprise.

Add an organization to your enterprise

You can create new organizations directly in your enterprise and transfer existing organizations into your enterprise.

Once an organization belongs to an enterprise, the only way to remove it from the enterprise is to delete the organization.

Transfer an organization to your enterprise

You can transfer an existing organization to your enterprise if all of the following conditions are met:

To transfer an existing organization to your enterprise, contact DataStax Support.

Create an organization in your enterprise

When you create an organization from the enterprise level, the organization automatically belongs to your enterprise.

If you want to create an organization that doesn’t belong to an enterprise, see the instructions to create a standalone organization.

  • Astra Portal

  • DevOps API

  1. In the Astra Portal header, click Settings.

  2. In the Settings navigation menu, click the name of the active organization or enterprise, and then select your enterprise.

  3. On your enterprise’s Overview page, click Create organization.

  4. Enter a name for the organization and an optional description.

    When you create an organization in the Astra Portal, you are the initial Organization Administrator. The Organization email defaults to your Astra account email address. After you create the organization, you can invite another Organization Administrator, and then change the organization email.

  5. Click Create organization.

To create an organization in your enterprise, use POST v2/enterprises/organizations:

curl -sS -L -X POST "https://api.astra.datastax.com/v2/enterprises/organizations" \
--header "Authorization: Bearer ENTERPRISE_APPLICATION_TOKEN" \
--header "Content-Type: application/json" \
--data '{
  "name": "ORG_NAME",
  "email": "ORG_EMAIL",
  "adminUserID": "ORG_ADMIN_ID",
  "enterpriseID": "ENTERPRISE_ID"
}'

Replace the following:

  • ENTERPRISE_APPLICATION_TOKEN: Your enterprise application token.

  • ORG_NAME: The name for the new organization.

  • ORG_EMAIL: The email address to receive administrative notifications related to this organization. Usually this is the email address of the user specified in adminUserID.

  • ORG_ADMIN_ID: The Astra user ID of the user who will be the initial Organization Administrator. The user must have an active Astra account.

    To get a list of users in an organization, including their user IDs, use GET /v2/organizations/users. For this endpoint to return the organization’s users, you must pass an organization application token, not an enterprise application token.

  • ENTERPRISE_ID: Your enterprise ID.

Result

A successful response returns an object containing organization details, including the new organization’s ID:

{
  "OrganizationName": "Example Org",
  "OrganizationID": "ORG_ID",
  "OrganizationEmail": "admin@acme-enterprises.com",
  "MarketplaceData": {},
  "CreatedAt": "2024-06-14T15:41:45.395919529Z",
  "LastModified": "2024-06-14T15:41:45.395919529Z",
  "OrgType": "organization",
  "EnterpriseId": "ENTERPRISE_ID",
  "OrganizationGroupId": "ORG_GROUP_ID"
}

DataStax uses the organizationGroupId to track organization usage for your enterprise.

Remove an organization from your enterprise

After you add an organization to your enterprise, you cannot transfer it out of your enterprise. To remove an organization, you must delete it. For instructions and more information, see Delete an organization.

Manage enterprise billing and usage

On your enterprise’s Overview page, you can get a summary of enterprise-wide usage, and you can download monthly usage reports for all organization in your enterprise.

For all other billing information and management, you must use the DevOps API or access each organization’s billing settings in the Astra Portal:

Download a complete monthly enterprise usage report

  • Astra Portal

  • DevOps API

In the Astra Portal, you can download a usage report CSV for all organizations in an enterprise:

  1. In the Astra Portal header, click Settings.

  2. In the Settings navigation menu, click the name of the active organization, and then select your enterprise.

  3. In the Settings navigation menu, click Overview.

  4. In the Usage Reports section, click Usage reports, and then select Download daily usage (CSV) to download usage history for the given month.

  5. Open and review the usage report.

    Usage report contents

    The usage report CSV file includes the following columns:

    • PRODUCT: The name of the Astra product or service generating usage.

    • ORG_ID: The organization ID.

    • ORG_NAME: The organization name.

    • RESOURCE_ID: The ID of the resource generating usage, such as a database or streaming tenant.

    • RESOURCE_NAME: The resource name.

    • REGION: The region where the resource is deployed and generating usage.

    • CLOUD_PROVIDER: The cloud provider that hosts the given REGION.

    • CLASSIFICATION: The region pricing classification, such as standard or premium.

    • ZONE: Indicates if usage is coming from a specific zone, including na (North America), apac(Asia Pacific), or emea (Europe, Middle East, Africa).

    • CLUSTER_SIZE: For Astra DB Classic databases, this is the cluster size, such as c10 or c20. For Astra DB Serverless databases, this is empty.

    • AZ_COUNT: For Astra DB Serverless databases, this is 3 because these databases are triple replicated to three availability zones. For Astra DB Classic databases this is empty regardless of actual replication.

    • USAGE_TYPE: The specific type of usage that was generated.

    • USAGE: The amount of usage generate.

    • USAGE_UNIT: The unit of measurement for USAGE, such as hour, gib, or million.

    • CURRENCY_TYPE: The currency type used for billing.

    • UNIT_PRICE: The price per unit of usage in the given CURRENCY_TYPE.

    • CALCULATED_COST: The total cost for an amount of USAGE during the given time period defined by the TIMESTAMP columns.

    • BREAKDOWN_START_TIMESTAMP: The beginning of the period for which usage was calculated.

    • BREAKDOWN_END_TIMESTAMP: The end of the period for which usage was calculated.

Use the DevOps API to generate and download a detailed monthly usage report for all organizations and resources in your enterprise.

It can take some time to generate the report, depending on the number of organizations and resources in your enterprise, because this report contains detailed usage data. To get usage summaries for specific organizations or resources, see Get filtered usage for a specific time range and Get filtered usage for the current month.

  1. Initialize report generation:

    curl -sS -location -X POST "https://api.astra.datastax.com/v2/enterprises/billing-reports/generate-report" \
--header "Authorization: Bearer ENTERPRISE_APPLICATION_TOKEN" \
--header "Content-Type: application/json" \
--data '{
  "month": "REPORT_MONTH_NUMBER_STRING",
  "year": "REPORT_YEAR_NUMBER_STRING"
}'

    Replace the following:

    • ENTERPRISE_APPLICATION_TOKEN: Your enterprise application token.

    • REPORT_MONTH_NUMBER_STRING and REPORT_YEAR_NUMBER_STRING: The month and year for which you want to generate the report represented as string-formatted numbers, such as "02" and "2025".

      This endpoint cannot retrieve data prior to November 2024.

  2. From the response, get the reportId.

  3. Get a link to download the generated report as a CSV file:

    curl -sS -location -X GET "https://api.astra.datastax.com/v2/enterprises/billing-reports/REPORT_ID" \
--header "Authorization: Bearer ENTERPRISE_APPLICATION_TOKEN" \
--header "Content-Type: application/json"

    Replace the following:

    • ENTERPRISE_APPLICATION_TOKEN: Your enterprise application token.

    • REPORT_ID: The reportId returned from /v2/enterprises/billing-reports/generate-report.

  4. From the response, use the csvDownloadUrl to retrieve the generated report.

    The availability of the download link depends on the report status:

    • PENDING: The report is queued for generation

    • INITIATED: The report is being generated

    • COMPLETED: The report is ready for download

    • FAILED: The report failed to generate

  5. Open and review the usage report.

    Usage report contents

    The usage report CSV file includes the following columns:

    • PRODUCT: The name of the Astra product or service generating usage.

    • ORG_ID: The organization ID.

    • ORG_NAME: The organization name.

    • RESOURCE_ID: The ID of the resource generating usage, such as a database or streaming tenant.

    • RESOURCE_NAME: The resource name.

    • REGION: The region where the resource is deployed and generating usage.

    • CLOUD_PROVIDER: The cloud provider that hosts the given REGION.

    • CLASSIFICATION: The region pricing classification, such as standard or premium.

    • ZONE: Indicates if usage is coming from a specific zone, including na (North America), apac(Asia Pacific), or emea (Europe, Middle East, Africa).

    • CLUSTER_SIZE: For Astra DB Classic databases, this is the cluster size, such as c10 or c20. For Astra DB Serverless databases, this is empty.

    • AZ_COUNT: For Astra DB Serverless databases, this is 3 because these databases are triple replicated to three availability zones. For Astra DB Classic databases this is empty regardless of actual replication.

    • USAGE_TYPE: The specific type of usage that was generated.

    • USAGE: The amount of usage generate.

    • USAGE_UNIT: The unit of measurement for USAGE, such as hour, gib, or million.

    • CURRENCY_TYPE: The currency type used for billing.

    • UNIT_PRICE: The price per unit of usage in the given CURRENCY_TYPE.

    • CALCULATED_COST: The total cost for an amount of USAGE during the given time period defined by the TIMESTAMP columns.

    • BREAKDOWN_START_TIMESTAMP: The beginning of the period for which usage was calculated.

    • BREAKDOWN_END_TIMESTAMP: The end of the period for which usage was calculated.

Get filtered usage for the current month

Get a usage summary for the current month, optionally filtering on specific organizations or resources. To get usage for previous months or periods shorter than one month, see Get filtered usage for a specific time range.

curl -sS -L -X POST "https://api.astra.datastax.com/v2/enterprises/consumption" \
--header "Authorization: Bearer ENTERPRISE_APPLICATION_TOKEN" \
--header "Content-Type: application/json" \
--data '{
  "organizations":
  [
    {
      "orgId": "ORGANIZATION_ID",
      "products": [
        {
          "productName": "pcu",
          "resourceIds": [
            "RESOURCE_ID",
            "RESOURCE_ID"
          ]
        }
      ]
    }
  ]
}'

Replace the following:

  • ENTERPRISE_APPLICATION_TOKEN: Your enterprise application token.

  • ORGANIZATION_ID: Provide one or more organization IDs to retrieve usage for specific organizations in your enterprise. If you specify multiple organizations, each organization must belong to its own object within the organizations array.

    To retrieve usage for all organizations in your enterprise, omit organizations. However, DataStax recommends specifying at least one organization due to the amount of data this request can return for enterprises with many organizations. If you need to get usage data for your entire enterprise, consider downloading an enterprise usage report CSV file.

  • PRODUCT_NAME and RESOURCE_ID: products is an optional array that you can use to retrieve usage for specific resources in an organization.

    If included, the products array consists of one or more objects, where each object contains a productName string and an array of resourceIds. For example, the following products object queries two Astra DB Serverless databases:

          "products": [
        {
          "productName": "serverless",
          "resourceIds": [
            "dda7ced6-e615-4023-8e7a-1e4429d43437",
            "0985a909-ecef-46e0-acf2-e1a8ebd51485"
          ]
        }
      ]

    Valid values for productName include serverless (Astra DB Serverless databases), managed_cluster (Astra DB Classic databases), pcu, or streaming (Astra Streaming tenants).

    To retrieve usage for all resources associated with a specific product, omit resourceIds or pass an empty array. To retrieve usage for all products and resources, omit products.

    For examples of product names and resource IDs, send a request without products. The response includes usage for products, including productName and resourceId values that you can use to filter subsequent requests.

A successful response returns the following usage summary data:

  • totalCost: Total cost for the queried usage (current month, organization, products, and resources).

  • currencyType: The currency in which costs are calculated.

  • creditsInfo: The type of credits, based on the subscription plan.

  • total: Total credits available for the current month.

  • consumed: Credits consumed in the current month.

  • remaining: Credits remaining for the current month.

  • organizations: An array of objects providing usage and cost breakdowns by organization, further subdivided by products and resources. Individual resources can be broken into additional usage categories, such as regional usage.

To get a detailed usage report, see Download a complete monthly enterprise usage report.

Get filtered usage for a specific time range

Get a usage summary for a specific time range of up to 31 days, optionally filtering on specific organizations or resources:

curl -sS -L -X POST "https://api.astra.datastax.com/v2/enterprises/consumption" \
--header "Authorization: Bearer ENTERPRISE_APPLICATION_TOKEN" \
--header "Content-Type: application/json" \
--data '{
  "fromDate": "START_DATE_TIME",
  "toDate": "END_DATE_TIME",
  "organizations":
  [
    {
      "orgId": "ORGANIZATION_ID",
      "products": [
        {
          "productName": "pcu",
          "resourceIds": [
            "RESOURCE_ID",
            "RESOURCE_ID"
          ]
        }
      ]
    }
  ]
}'

Replace the following:

  • ENTERPRISE_APPLICATION_TOKEN: Your enterprise application token.

  • START_DATE_TIME and END_DATE_TIME: An optional date range for which you want to retrieve usage details. The entire range cannot exceed 31 days, and both dates must be in ISO RFC3339 format, such as "2021-05-06T06:13:23.57Z".

    This endpoint cannot retrieve data prior to November 2024.

  • ORGANIZATION_ID: Provide one or more organization IDs to retrieve usage for specific organizations in your enterprise. If you specify multiple organizations, each organization must belong to its own object within the organizations array.

    To retrieve usage for all organizations in your enterprise, omit organizations. However, DataStax recommends specifying at least one organization due to the amount of data this request can return for enterprises with many organizations. If you need to get usage data for your entire enterprise, consider downloading an enterprise usage report CSV file.

  • PRODUCT_NAME and RESOURCE_ID: products is an optional array that you can use to retrieve usage for specific resources in an organization.

    If included, the products array consists of one or more objects, where each object contains a productName string and an array of resourceIds. For example, the following products object queries two Astra DB Serverless databases:

          "products": [
        {
          "productName": "serverless",
          "resourceIds": [
            "dda7ced6-e615-4023-8e7a-1e4429d43437",
            "0985a909-ecef-46e0-acf2-e1a8ebd51485"
          ]
        }
      ]

    Valid values for productName include serverless (Astra DB Serverless databases), managed_cluster (Astra DB Classic databases), pcu, or streaming (Astra Streaming tenants).

    To retrieve usage for all resources associated with a specific product, omit resourceIds or pass an empty array. To retrieve usage for all products and resources, omit products.

    For examples of product names and resource IDs, send a request without products. The response includes usage for products, including productName and resourceId values that you can use to filter subsequent requests.

A successful response returns the following usage summary data:

  • totalCost: Total cost for the queried usage (current month, organization, products, and resources).

  • currencyType: The currency in which costs are calculated.

  • creditsInfo: The type of credits, based on the subscription plan.

  • total: Total credits available for the current month.

  • consumed: Credits consumed in the current month.

  • remaining: Credits remaining for the current month.

  • organizations: An array of objects providing usage and cost breakdowns by organization, further subdivided by products and resources. Individual resources can be broken into additional usage categories, such as regional usage.

To get a detailed usage report, see Download a complete monthly enterprise usage report.

Manage enterprise users and roles

Enterprise role-based access control (RBAC) allows you to separate enterprise access from organization access.

Enterprise RBAC isn’t a global RBAC tool.

Enterprise access is separate from organization access. For example, an Enterprise Administrator cannot manage resources in an organization unless they are also an Organization Administrator in that organization.

When managing enterprise users and roles, consider your enterprise’s security policies and industry best practices for RBAC, such as the principle of least privilege. For more information about RBAC in Astra DB, see Manage roles and permissions.
Enterprise users

Enterprise membership is separate from organization membership. Users can belong to an enterprise without belonging to any organizations, and they can belong to individual organizations without access to the enterprise level.

By default, an enterprise invitation adds a user to the enterprise only.

If you want to add user to your enterprise and one or more organizations, you must send separate invitations for the enterprise and each organization. The same principle applies to removing users and editing user roles.

Memberships are managed separately to support the separation of duties and the principle of least privilege throughout the entire enterprise hierarchy. For example, a user who is a Database Administrator in one organization might not need the same level of access in another organization.

For instructions and more information, see Manage users.

Enterprise roles and permissions

Enterprise roles are separate from organization roles. The actions that a user can take at the enterprise level depend on the user’s enterprise role. The actions that a user can take within a specific organization depend on the user’s role in that organization.

You can create custom enterprise roles or use the default enterprise roles:

For more information about enterprise permissions and creating custom enterprise roles, see Manage roles and permissions.

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2025 DataStax | Privacy policy | Terms of use | Manage Privacy Choices

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: +1 (650) 389-6000, info@datastax.com