Every SOP. Every setting. One repository your team actually trusts.
SOPR is where your organization's procedures, configurations, and the credentials behind them live — centralized, kept current, and locked down properly instead of scattered across shared drives, sticky notes, and someone's personal notebook.
Every procedure, credential, and config — one locked-down repository.
A quick look at how SOPR organizes your assets, secrets, and access in one place.
Procedures written once, found by everyone who needs them.
Every standard operating procedure lives in one searchable place instead of whichever chat thread or shared folder it happened to be written in. A consistent structure means a new hire and a ten-year veteran read the same step-by-step process the same way.
Templates keep every article in the same shape — the same headings, the same level of detail — so documentation quality doesn't quietly depend on who happened to write it that week.
Passwords and configuration details, stored the way they should be.
The credentials, license keys, and configuration values behind your procedures don't belong in a spreadsheet. SOPR keeps them encrypted at rest, masked by default, and revealed only to someone who's actually supposed to see them.
A procedure can reference the exact setting it depends on without that setting ever sitting in plain text where anyone browsing the document library could copy it.
A client, a site, a system, a procedure — connected, not scattered.
Real operations aren't flat lists. SOPR lets you relate a procedure to the specific client, location, or piece of equipment it actually applies to, so anyone looking at an asset can see every document and credential tied to it — and anyone reading a procedure can see exactly where it applies.
That structure is what turns a folder of documents into an actual repository — one where "where's the SOP for this?" has a fast, reliable answer.
Access is granted deliberately. Every look is on the record.
Not everyone on the team needs to see every credential. Permissions in SOPR are granular by design, so a contractor can be handed exactly the procedures they need without inheriting the keys to everything else.
Every view, edit, and credential reveal is recorded, so if something changes — or someone asks who looked at what — the answer is a lookup, not a guess.
The repository holding your credentials has to earn that trust first.
SOPR is built around the assumption that what's stored in it — configurations, credentials, internal procedures — is exactly the kind of information that shouldn't leak. That's reflected in how access, storage, and visibility are handled throughout.
Encrypted storage, always
Configuration values and credentials are encrypted at rest and masked by default — visible only to someone who deliberately reveals them, not to anyone browsing the repository.
Granular, role-based access
Permissions apply down to individual procedures and credentials, not just the repository as a whole — so access can match exactly what a role actually needs.
A full audit trail
Every view, edit, and credential reveal is logged with who and when, so accountability doesn't depend on anyone's memory.
Mandatory two-factor authentication
Every account requires a second factor to sign in — there's no setting to turn it off.
Encrypted in transit
Every connection to the repository, in both directions, travels over an encrypted connection.
Version history, kept
Procedures change as your operations do. Past versions stay recoverable, so an edit is never a one-way door.
Stop keeping your procedures somewhere you're not sure about.
SOPR is a separate, dedicated application in the IQBaseline family — built specifically to be the one place your team's SOPs and configurations actually live.
Open SOPR ↗