Policies

Joopler ships a starter library of security policies mapped to your controls. You review each one, adopt it, and collect employee acceptance, all tracked so you can prove coverage.

Adopt a policy

Each starter policy arrives as Seeded - a template we provide, not something adopted on your behalf. Review it, edit if needed, and approve it. On approval the policy version is signed and timestamped, and it moves to Approved.

You can also tailor a policy to your actual environment: Joopler grounds the draft in the systems, cloud, and data types you have connected, so the policy reflects your setup rather than generic boilerplate.

Versioning and acceptance

• Acceptance is tracked per person. Employees accept the policies that apply to them; their acceptance is recorded against the exact version they saw.
• A new version invalidates old acceptances. When you publish a new version, prior acceptances no longer count and a re-acceptance campaign asks the affected people to accept the current version.
• For full coverage, keep your workforce current on the People page so everyone who should accept a policy is on the roster.

Sign-off

Policy approval is a human act, done by an owner or admin, and is signed into the evidence ledger. That signature is what an auditor relies on - Joopler records the claim, a person makes it.