Security and trust
Keep company learning inside your Atlassian environment
Peercraft is built on Atlassian Forge and designed for one company per Confluence installation.
Course ownership is checked on the server. Learner progress remains private to each account. Each installed site has its own course library and data.
Built on Atlassian Forge
Peercraft runs on Atlassian's own app infrastructure. There is no separate Peercraft server to vet, monitor, or maintain. Your learning platform lives where your knowledge already does.
Per-site data storage
Peercraft is designed for one company per Confluence installation. Each installed site has its own course library and its own data.
Server-side permission checks
Course ownership is checked on the server, not in the browser. Permission checks protect who can edit, publish, and manage every course.
Private learner progress
Learner progress remains private to each account. Managers see completion where it matters; individual learning activity stays with the learner.
Verified Atlassian identities
Peercraft uses the Atlassian user identities your organisation already manages. No separate accounts, passwords, or user directories.
Sanitised course content
Rich-text course content is sanitised before it is stored and rendered, protecting your site from unsafe markup.
Automated testing
Automated tests run across the frontend and backend, so changes to Peercraft are verified before they reach your site.
Read-only licence fallback
If a licence lapses, Peercraft falls back to read-only mode. Your courses and learning records stay intact and accessible.
Bring your IT and security questions to the demo
We are happy to walk your Atlassian administrators through how Peercraft stores data, checks permissions, and runs on Forge.