Your Community Platform Starts Here – Try the Demo Today

Log in
Sign up
Log in
Sign up

Your Community Platform Starts Here – Try the Demo Today

Log in
Sign up
Log in
Sign up
Sign up
Log in

Usage limits best practices

Builda includes usage for certain resources and features. Your organization can monitor and control how that usage is allocated across your account and individual users.

Builda may measure different types of usage separately, including:

  • Computing
  • Notifications
  • Storage
  • Contact info unlocks
  • AI credits
  • Other usage-based features or resources

Your Builda subscription includes a minimum monthly usage amount based on the number of users in your organization. This minimum monthly amount is billed regardless of how much usage your organization consumes during that month.

Unused included usage does not roll over to future months.

Authorized administrators can control usage at both the account level and individual user level, including allowing usage beyond the amount included with the subscription.

Your Builda account shows your organization’s usage, configured limits, and applicable usage information.

Understanding your usage

Computing

Computing represents processing resources used by certain Builda features and actions.

Computing usage may vary depending on factors such as:

  • The feature being used
  • The amount of data being processed
  • The complexity of the action
  • Automations or workflows
  • Background processing
  • Integrations
  • Multi-step operations
  • Other processing-intensive activity

Different actions may use different amounts of computing.

A simple action may require substantially less computing than an automation or operation involving larger amounts of data.

Notifications

Notification usage applies when Builda sends supported notifications on behalf of your organization.

Usage may vary depending on factors such as:

  • The notification channel
  • The number of recipients
  • The number of notifications sent
  • The feature generating the notification
  • Automated notification activity

Sending the same notification to multiple recipients may result in usage for each recipient.

Different notification types or channels may consume different amounts of usage.

Storage

Storage includes eligible files, attachments, documents, media, and other content stored by your organization within Builda.

Storage usage may be affected by:

  • File size
  • Number of files
  • Attachments
  • Images and media
  • Documents
  • Content uploaded by users
  • Other stored data counted toward your account

Larger files and greater amounts of stored content use more of your available storage.

Removing content that is no longer needed can help reduce storage usage where applicable.

Contact info unlocks

Certain Builda features may allow users to unlock available contact information.

An unlock uses the applicable amount of usage associated with that action.

Usage may vary depending on the information being unlocked or the feature being used.

The availability, completeness, and accuracy of contact information can vary. Contact information should only be used for lawful purposes and in accordance with applicable privacy, marketing, communications, and data protection laws.

AI credits

AI credits are used when eligible AI-powered features are used within Builda.

The amount of AI usage required may vary depending on factors such as:

  • The AI feature being used
  • Model selection
  • Prompt or input length
  • Output length
  • Files or data being analyzed
  • Task complexity
  • Tool usage
  • Multi-step AI tasks
  • Other processing required to complete the request

More complex AI requests may consume more usage than simple requests.

Where applicable, Builda may display the amount or type of AI usage associated with a feature.

How monthly usage works

Your Builda subscription includes a minimum monthly usage amount based on the number of users in your organization.

This minimum amount is billed each month regardless of whether your organization uses all of the included usage.

Unused included usage expires at the end of the applicable monthly usage period and does not roll over to a future month.

If your organization consumes more than the included monthly usage, additional usage may be billed at the applicable rates.

Your administrators can control how much usage is permitted by configuring account-level and user-level limits.

How usage limits work

Builda allows authorized administrators to control usage at both the account level and individual user level.

Depending on your organization’s needs, administrators may configure limits to:

  • Match the included usage available to an individual user
  • Match the total included usage available to the organization
  • Restrict usage below the included amount
  • Allocate different limits to different users
  • Allow usage beyond the included amount by increasing the applicable limit

Account-level limits control the maximum usage permitted across your organization.

User-level limits control how much usage an individual user is permitted to consume.

User-level limits remain subject to any applicable account-level limit.

Increasing a limit may allow additional usage beyond the amount included with your subscription.

Included and additional usage

Your Builda subscription includes a minimum monthly amount of usage based on your number of users.

You are billed for this minimum monthly amount regardless of actual usage.

If your organization uses less than the included amount during the month, the unused portion does not carry forward.

If an administrator allows usage beyond the included monthly amount, your organization may incur additional usage charges at the applicable rates.

Increasing a usage limit does not itself mean the full limit will be charged. Additional usage charges, where applicable, are based on actual usage consumed beyond the included amount.

Administrators should review account and user limits carefully before increasing them.

Account-level usage limits

Account-level limits allow your organization to control the maximum amount of applicable usage permitted across the account.

For example, an administrator may choose to:

  • Limit the organization to its included monthly usage
  • Set a lower limit to control consumption
  • Allow additional usage by setting a higher limit

Once the applicable account-level limit is reached, affected usage may be restricted until:

  • A new usage period begins, or
  • An authorized administrator increases the applicable limit

User-level usage limits

User-level limits allow administrators to control how much applicable usage individual users can consume.

This can help organizations:

  • Prevent a single user from consuming excessive usage
  • Allocate more usage to users who need it
  • Restrict usage for certain users
  • Manage usage across larger teams
  • Allow specific users to exceed their included per-user amount when appropriate

A user’s configured limit does not necessarily reserve that amount of usage exclusively for that user.

Increasing an individual user’s limit also does not override an account-level limit that has already been reached.

What happens when a usage limit is reached?

What happens depends on which limit is reached.

If a user-level limit is reached, the affected user may be unable to continue using the applicable resource until:

  • A new usage period begins, where applicable, or
  • An authorized administrator increases that user’s limit

If an account-level limit is reached, applicable usage may be restricted across the organization until:

  • A new usage period begins, where applicable, or
  • An authorized administrator increases the account-level limit

Reaching one type of usage limit does not necessarily prevent the use of other Builda features or resources that remain available.

Builda may notify administrators or users when certain limits are approaching or have been reached.

1. Monitor your usage

Review your organization’s usage regularly so you know how much has been consumed and how your limits are configured.

Pay particular attention to resources your organization uses frequently, such as:

  • Computing
  • Notifications
  • Storage
  • Contact info unlocks
  • AI credits

Monitoring usage can help administrators identify unusually high activity and adjust limits when necessary.

2. Set appropriate account limits

Your account-level limits are an important way to control organization-wide usage.

Consider setting limits based on:

  • Expected usage
  • Your organization’s budget
  • Number of users
  • Historical consumption
  • Features your organization uses most frequently

Increase limits only when your organization intends to allow usage beyond the included monthly amount.

3. Set appropriate user limits

Not every user needs the same amount of usage.

Consider assigning limits based on each user’s role and expected activity.

Users who regularly work with AI, contact information, automations, or other usage-intensive features may require higher limits than users who use those features less frequently.

Review user limits periodically as responsibilities change.

4. Keep stored content organized

Periodically review stored content and remove items your organization no longer needs.

When possible:

  • Avoid unnecessary duplicate files.
  • Remove obsolete files.
  • Replace outdated documents instead of keeping unnecessary copies.
  • Compress large files when appropriate.
  • Keep frequently used information organized and centralized.

This can help your organization use storage more efficiently.

5. Use notifications efficiently

Avoid sending unnecessary or duplicate notifications.

Before sending notifications to large groups:

  • Confirm the correct audience.
  • Avoid unnecessary duplicate sends.
  • Review automated notification settings.
  • Use the appropriate notification channel.

Automations can generate notification usage without requiring someone to manually send each notification, so review active automations periodically.

6. Use computing efficiently

Computing-intensive actions can consume more resources than simple activity.

When practical:

  • Avoid running unnecessary processes.
  • Review automations that run frequently.
  • Disable workflows that are no longer needed.
  • Avoid repeatedly processing the same information unnecessarily.
  • Review integrations or processes generating unusually high activity.

7. Unlock contact information intentionally

Only unlock contact information when it is relevant to your work.

Before unlocking information:

  • Confirm that the contact is relevant.
  • Avoid unnecessary or duplicate unlocks.
  • Use unlocked information only for legitimate and lawful purposes.

This helps your organization make better use of its available contact info usage.

8. Use AI efficiently

Clear and complete instructions can reduce unnecessary AI usage.

When using Builda’s AI features:

  • Clearly describe what you need.
  • Include relevant context in your initial request.
  • Combine closely related requests when practical.
  • Avoid unnecessarily repeating the same request.
  • Provide only the files and information needed for the task.
  • Use the appropriate AI feature for the job.

Complex tasks, large inputs, long outputs, files, tools, and multi-step requests may consume more AI usage.

9. Review automations and recurring activity

Automations can continue generating usage even when nobody is actively using Builda.

Periodically review:

  • Automated workflows
  • Scheduled actions
  • Notifications
  • Integrations
  • AI-powered automations
  • Recurring processes

Disable anything your organization no longer needs.

Usage calculations

Builda measures usage using its systems and the applicable measurement method for each resource.

Because different features consume different resources, individual actions may not always consume the same amount of usage.

Usage calculations may depend on the feature, activity, processing required, and other factors associated with the action.

The usage information displayed in your Builda account reflects Builda’s measurement of your organization’s usage.

Usage controls and administrator responsibility

Usage limits are controls configured by authorized administrators.

Increasing a limit may allow users or your organization to incur usage beyond the amount included with your Builda subscription.

Administrators are responsible for reviewing and managing these limits based on their organization’s needs and authorized spending.

Setting a higher limit does not guarantee or reserve that amount of usage and does not itself create an additional charge. Additional charges, where applicable, result from actual usage beyond the amount included with your subscription.

The minimum monthly subscription amount remains payable regardless of whether all included usage is consumed.

Account-specific terms

This article provides general information about how Builda usage and usage limits work.

Your specific included usage, rates for additional usage, measurement methods, and other applicable usage terms are shown in Builda or provided as part of your subscription or agreement with Builda LLC.

If your organization has an Order Form, enterprise agreement, promotional offer, or other written agreement with Builda LLC that provides different terms, that agreement governs.

Subscription pricing, billing, renewals, cancellations, refunds, taxes, and other account terms are governed by the applicable Builda terms and agreements.