Connecting Elements.cloud to your Salesforce Production Org is designed to be low-impact, both in terms of API usage and platform limits. Below is a clear breakdown of what to expect.
What Elements connection DOES NOT do
There are a few key things to keep in mind when you are assessing impact of connecting your Production Org to Elements.cloud:
We never modify your org configuration
We never slow down user transactions
We never interfere with flows or Apex execution
We never replicate your actual customer data
API Usage Impact
When an Org is connected, Elements performs a daily metadata sync to ensure the metadata intelligence is accurate and up to date every day. This connection consumes API calls and contributes to your daily API request limit.
Because Elements only looks at and syncs your Configuration Metadata, there is no difference between syncing Sandbox vs Production Orgs. The impact on both Orgs will be exactly the same.
Connecting a new Org
When you first connect an Org to Elements, we need to sync all of your metadata. This is a bigger operation, and the size of the job completely depends on the size and complexity of your Org.
Example 1 (Enterprise Edition, Moderately complex Org, 20 licenses users):
Total limit: 120,000 API calls / 24h
First sync usage: ~16,000 API calls
Usage: ~13% of daily limit
Example 2 (Enterprise Edition, Complex Org, 500 licenses users):
Total limit: 600,000 API calls / 24h
First sync usage: ~31,000 API calls
Usage: ~6% of daily limit
Every next sync
Each subsequent sync consumes a very small fraction of API calls because we only check what has changed in your Org and get details for created, modified or deleted metadata.
To illustrate, let's show two examples:
Example 1 (Enterprise Edition, Moderate complexity Org, 20 licenses users):
Total limit: 120,000 API calls / 24h
Typical 'daily' sync usage: ~1,600 API calls per day
Usage: ~1.3% of daily limit
Example 2 (Enterprise Edition, Complex Org, 500 licenses users):
Total limit: 600,000 API calls / 24h
Typical 'daily' sync usage: ~2,583 API calls per day
Usage: ~0.4% of daily limit
Conclusion
Elements consumes a very small fraction of available API capacity. Across many customer implementations, API limits have not been a constraint caused by Elements.
The more users you have in your Org, the higher your daily API usage limit, the more negligible Elements usage becomes.
Managed Package Impact (Optional)
Installing the Elements managed package enables deeper analysis capabilities. This introduces limited additional activity:
Scheduled Apex Jobs
Up to 3 scheduled jobs
Run 3 times per day (though 2 of the 3 jobs can be scheduled to run weekly!)
The Record Information job has approx 10 executions per run
The Profile Metadata job has approx 2 executions per run
The record audit job has approx 3 executions per run
Contribute to:
Scheduled job limit: 100 (3%)
Maximum daily Apex execution limit: 15 (0.006% of the total daily limit)
Impact
Negligible. These jobs represent a very small proportion of available capacity.
Optional: Auto User Provisioning
If enabled, auto-provisioning introduces:
An Apex trigger on the User object
Automatically:
Provisions new users into Elements
Handles deactivation/removal logic
Important:
This feature is optional
It only executes when User records are created or updated
Impact:
Minimal for most orgs. However, orgs with very high user provisioning volume (e.g. large-scale automated user creation) should consider this in their governance model.
Summary
Area | Impact Level | Notes |
API Usage | Very Low | ~1,600 calls/day |
Scheduled Apex Jobs | Very Low | 3 jobs, low execution runs |
Auto User Provisioning | Optional | Trigger on User object |
Key Takeaway
For the vast majority of Salesforce customers, connecting Elements.cloud to Production has no material impact on API limits or platform performance. The design intentionally minimizes resource consumption while enabling powerful metadata analysis and insights.