Welcome to Storacle!
Your installation is complete. Follow these quick steps to finish setup and start monitoring your Salesforce storage.
Quick Start: Open Storacle Home
Navigate to the Storacle app in your Salesforce org to complete setup:
Replace [your-domain] with your Salesforce My Domain (e.g., acme or acme--sandbox)
Complete Your Setup
Open the Storacle App
In Salesforce, use the App Launcher (9-dot grid icon) and search for "Storacle", or navigate directly using the URL above. You'll land on the Storacle Home page.
Configure Credentials
When you first open Storacle, a setup modal will appear. Click the "Configure" button to create the necessary Named Credential for your org.
Authorize Access
Click the "Authorize" button. This opens the External Credentials page in Salesforce Setup. Find the Storacle credential and click "Authenticate" to complete the OAuth flow.
Your Data Stays In Your Org
The credentials and authorization you just configured are purely internal. They allow the Storacle app—which runs entirely within your Salesforce org—to access your org's REST API for storage measurements.
- No external connections: Storacle does not send data to, or receive data from, any external servers or services.
- Runs inside your org: All Storacle code executes within your Salesforce environment using standard Apex and Lightning components.
- Org-to-org API access: The Named Credential enables Storacle's engine to call your org's own REST API endpoints (like /limits) to gather storage metrics.
- Data stays local: All measurement data is stored in custom objects within your org—never transmitted externally.
Enable the Engine
Return to the Storacle Home page. Once setup is complete (status shows green), toggle the Engine switch to start automated daily storage measurements.
How Storacle Connects to Your Org
To measure your storage, Storacle's engine reads your org's own limits and storage API—the same information you'd see on the Salesforce Storage Usage page. Salesforce treats even a call back to your own org as an external API callout, and it requires an authenticated connection to make one. The setup process creates a short chain of standard Salesforce components that provide that authentication. Here's what each one is for.
Certificate
A cryptographic certificate that signs the token Storacle uses to prove its identity when it authenticates to your org's API. The private key never leaves your org.
External Client App
The OAuth application Storacle authenticates through to obtain a short-lived access token. It defines the connection and limits it to only the access the engine needs.
External Credential
Holds the authentication settings—the protocol, the client app, and the signing certificate—that Storacle presents on each callout. This is the component you authorize during setup.
Named Credential
Defines the endpoint Storacle calls—your org's own API—and ties it to the External Credential so every request is authenticated. This is the "your org calling itself" connection the engine uses to read storage data.
The "operation test" is expected—and safe
During and after setup, Storacle runs an operation test that makes a real, authenticated call to your org's API to confirm the connection works. If you see this test—or notice the components above appear in Setup—there is nothing to worry about: they are created by Storacle on purpose, they only allow your org to talk to itself, and no data is ever sent to Storacle or any outside service.
Everything stays inside your Salesforce org. The chain of components exists solely because Salesforce requires an authenticated connection before any code—including code that only reads your own org—can call the API.
What to Expect
First Measurement
Your first storage measurement will run when you enable the engine or click "Run Now". This captures a baseline of your current storage usage across all objects.
Daily Tracking
Once enabled, Storacle automatically measures storage daily. After a few days, you'll start seeing growth trends and can identify which objects are consuming the most space.
Reports & Dashboards
Storacle stores measurements in custom objects that you can report on. Build custom reports and dashboards to visualize storage trends over time.
Proactive Alerts
Set up threshold-based alerts to get notified when storage approaches critical levels, allowing you to take action before hitting limits.
Permission Sets
You're Already Set Up
As the installing user, you have already been assigned the Manager permission set. When you authorized the engine in Step 3, the Engine permission set was also granted to your user. You have everything you need to use Storacle.
Storacle includes three permission sets for different access levels:
Storacle Manager
Full administrative access including setup, configuration, and engine control.
Already assigned to: You (the installing admin)
Additional users: To assign the Manager permission set to other administrators, you must purchase additional Storacle Manager licenses from Salesforce AppExchange. Each manager user requires their own license.
Storacle Viewer
Read-only access to storage data, reports, and dashboards.
Storacle Engine
System-level access required for the automated measurement engine to run.
Important: This permission set was automatically granted to the user who authorized the engine (you). It should not be assigned to anyone else. The engine runs using the credentials of the authorizing user, and only that user needs this permission set.
Who the Engine Runs As
The measurement engine's scheduled runs happen under a specific user—its "run-as" user. That user's access is what the engine uses to read your storage data, so choosing it well matters.
Option 1: The installing admin (default)
By default, the engine runs as the administrator who authorized it during setup. This is the quickest way to get started and works well for most orgs. The trade-off is that the engine's runs depend on that user's account staying active—if the admin is later deactivated, the engine stops.
Option 2: A dedicated user (recommended for long-term use)
You can instead point the engine at a dedicated user set aside for it. This keeps automated measurement independent of any one person's account and makes it clear, when reviewing your org, why the connection exists.
License requirement: The run-as user must hold a license that permits API access and running scheduled Apex—typically a standard Salesforce license. The free Salesforce Integration license does not qualify, so it cannot be used as the engine's run-as user.
Need Help?
If you encounter any issues during setup or have questions, our support team is here to help.