Storacle Permissions
Three permission sets, four custom permissions, and the user permissions the engine needs. Here is what each one decides and how to hand one piece to someone else.
If you installed Storacle, you already hold what you need
A fresh install assigns the installer both the Storacle and the Storacle Administrator permission sets and puts them on the Storacle user list. That covers using Storacle, managing its users and seats, reaching billing, and scheduling the engine. This page is for giving someone else access, or for working out why a control is refusing someone.
A permission set is not a seat. Holding the Storacle set lets someone into Storacle. Whether they see the paid features is decided separately, by giving them a seat on the user list. Seats and the trial are explained on the Pricing page.
The three permission sets
All three ship in the package. Storacle creates no permission sets in your org.
Storacle
Assigned to: Everyone on the Storacle user list
The Use Storacle custom permission, the Storacle app and its tabs, and read access to the measurement records.
Storacle Administrator
Assigned to: The installer, on a fresh install
Manage Storacle Users, Manage Storacle Billing, and Run Storacle Engine.
Storacle Engine
Assigned to: Nobody, until you assign it
Run Storacle Engine, and the right to publish Storacle's own log events during a run.
The four custom permissions
Storacle decides who may do what by custom permission, not by permission set. The sets are just the packaged way to deliver them, which is what makes delegation possible.
Use Storacle
Carried by: Storacle
Marks someone as let in to Storacle. The user list flags anyone who holds it without being on the list, and that person can press Add me to Storacle on Storacle Home to join as a free user.
Manage Storacle Users
Carried by: Storacle Administrator
Administers the user list in Storacle Configuration: adding and removing people, and giving seats to and taking them back from the people on it. Nobody can remove themselves.
Manage Storacle Billing
Carried by: Storacle Administrator
Reaches this org's billing through Manage License Seats. The billing portal's Salesforce sign-in checks for it and refuses anyone without it. A holder who lacks Manage Storacle Users sees the seat counts and Manage License Seats, but not the list of people.
Run Storacle Engine
Carried by: Storacle Administrator and Storacle Engine
Lets the holder own the scheduled engine job. Schedule the Engine and Run Engine Now refuse anyone without it, and the engine schedule check reports a job whose owner is missing it.
Either Manage Storacle Users or Manage Storacle Billing opens the user and seat administration section of Storacle Configuration, and each of the two then allows only its own part of it.
What the engine's owner needs
The engine runs as whoever scheduled it, and Run Engine Now runs as whoever presses it. So the person who presses either one needs Run Storacle Engine and the three user permissions below. When they are short of any of them, Storacle disables the control and names what is missing.
API Enabled
The nightly measurement reads the org's own record counts through the Salesforce API.
View Setup and Configuration
Salesforce checks it before answering the record count read. Without it the read fails with an error that blames the org rather than the user.
View Roles
Salesforce will not save View Setup and Configuration without it, and Storacle checks for it in its own right.
A managed package cannot grant user permissions, so none of the three comes from a Storacle set. Grant them on the person's profile or on a permission set of your own. A System Administrator already holds all three.
Replacing an engine job that belongs to someone else also needs Modify All Data, because Salesforce requires it to remove a scheduled job another user owns.
To run the engine as a dedicated user, give that user the Storacle Engine set and the three user permissions, add them to the Storacle user list so they can open Storacle (this needs no seat), and have them press Schedule the Engine. The Setup Guide covers scheduling, and the Troubleshooting page covers an engine that reports it is not running.
Delegating one piece of administration
You do not have to hand someone the whole Storacle Administrator set. Put just the custom permission they need on a permission set of your own, or on a permission set group, and assign that. Storacle checks for the custom permission however it arrives.
- Someone in finance who pays for seats: Manage Storacle Billing alone. They can reach billing without seeing or changing who uses Storacle.
- Someone who manages access: Manage Storacle Users alone. They can add people and assign seats without reaching billing.
- Someone who looks after the engine: Run Storacle Engine, plus the three user permissions above.
The custom permission is the gate, not the way in. Each of these people also needs to open Storacle, so add them to the Storacle user list as well.
Still stuck?
If Storacle is missing from your App Launcher, or a control refuses you after you have granted what this page lists, see Troubleshooting or contact support.