What Procera does, and what it doesn't do yet

One governed home for policies (what and why) and SOPs (how), each with an owner, a version history and a lifecycle.

• Lifecycle: draft, in review, approved, scheduled or published, deprecated, retired
• Collections with per-collection visibility; restricted policies and applicability rules
• A Policies portal for employees, with what changed between versions
• Permission-filtered full-text search across documents and people

Tracker: BPMS-040, BPMS-041, BPMS-045, BPMS-049 done

Start from reviewed starter documents instead of a blank page. Everything installs as a draft for you to adapt, review and publish.

• Employee handbook pack: a handbook and four starter policies, plus a suggested acknowledgement campaign
• Core procedures pack: new starter onboarding and reporting an incident

The larger gallery of ready-made workflow templates (leave, expenses, purchasing, access and more) depends on the workflow engine and is planned with it.

No separate epic; verified by browser test E2E-R1-18

Ask people to read and acknowledge a specific version, chase them politely, and export evidence that stands up later.

• Audience as a snapshot or kept up to date; people who join later can be included automatically
• Reminders and manager escalation after the due date
• Each acknowledgement is bound to the version and its content hash
• Evidence CSV with version hash and sign-in method; progress by department

Tracker: BPMS-046 done

Targeted news and notices, with an optional confirm-by date and approval before anything goes out.

• Audience by department, group or location from the directory
• Schedule and expiry, pinned and critical posts
• Required confirmation with a confirm-by date, reminders and manager escalation
• Approval with separation of duties; reach and read receipts per post

Tracker: BPMS-047 done

Requests and approvals run on Procera's own workflow engine. Five ready-made request types work today, and owners can now design their own in the Guided Studio, test-run them and publish them.

• Leave, expense, purchase and access requests, routed to the requester's manager, finance, the CFO or IT by amount and sensitivity
• A request page with approval steps, timeline and cancel; a My Work inbox to approve, reject or send back with a comment
• Employee onboarding: IT, Facilities and the manager prepare at the same time, then the new member confirms equipment and handbook
• Nobody approves their own request; one decision wins when two people act at once; every step is in the audit trail
• Reminders before and at the due date; overdue manager approvals move up to the next manager, others alert the requester's manager
• Admins see unassigned and overdue steps and reassign them with a reason (separation of duties still applies)
• Guided Studio: a step builder for owners, with validation in plain language and test runs before publishing, plus a form builder with help, ranges, “show only when” questions, data classification and a phone preview, and a flow canvas that draws the same process as a diagram
• A conversation on every request: comments, internal notes the requester never sees, @mentions and watchers
• Operations view: technical incidents kept apart from people problems, retried or dismissed with a reason in the audit log
• Team workload for managers: who holds what, what is overdue, who is away with work waiting, and bulk reassign within the team
• Approve or reject from the email: the buttons open a confirm page through a single-use link, nothing is decided until you confirm
• Out of office: one click from the account menu; colleagues see who's away and who covers on hover; a delegate decides your approvals, recorded on your behalf, and separation of duties still applies to them
• Admins choose which request types are offered, who can ask for each, and the currency approval limits are read in
• Before sending, the form says who will approve it; files (receipts, quotes, photos) attach to requests and decisions, virus-scanned and previewable; each decision records the policy version the approver saw
• Parallel and quorum approvals (planned)

Tracker: BPMS-080, BPMS-081, BPMS-082, BPMS-083, BPMS-085, BPMS-086, BPMS-088, BPMS-100, BPMS-101, BPMS-103, BPMS-105 done

Invite people, import your org chart, and keep departments, managers and locations in one place.

• Invitations by email: single use, bound to the address, expiring after seven days
• CSV import with a check step that shows every row; manager cycles are refused
• Departments, groups, positions, managers and locations used for targeting
• Deactivating a member revokes their sessions immediately

Tracker: BPMS-023 done

A permission catalogue, built-in role templates and custom roles, granted to people or groups and scoped to a department or collection.

• 12 built-in role templates; custom roles cloned from them
• Grants scoped to the workspace, a department or a collection
• A preview of who gains or loses what before you save
• No escalation: you can't grant a permission you don't hold

Tracker: BPMS-024 done

Every change and every sensitive read is recorded in a per-workspace hash chain. Records can't be edited or deleted.

• Tamper-evident chain with verification in the product
• Explorer with filters, person and document timelines, and saved queries
• CSV and JSONL exports that need step-up and are themselves audited
• Background exports for large ranges

Tracker: BPMS-026, BPMS-064 done

Strong local sign-in out of the box, with two-step verification that admins can require by role.

• Argon2id passwords, breached-password rejection, lockout and rotating sessions
• Authenticator apps (TOTP), recovery codes, and passkeys or security keys
• Step-up confirmation for sensitive actions
• Workspace isolation enforced by PostgreSQL row-level security

Tracker: BPMS-021, BPMS-022, BPMS-025 done

Attachments are checked, encrypted and governed. Most of the pipeline works end to end; parts are still being finished.

• Resumable uploads, SHA-256 and content-based type detection; executables, scripts, HTML and SVG are refused
• Malware scanning through ClamAV, with quarantine
• Per-file encryption under the workspace key; short-lived signed links
• In-app previews of images, PDF (pages, zoom, search), Word and spreadsheets in a sandbox; retention classes honoured by jobs

Tracker: BPMS-060, BPMS-061, BPMS-062, BPMS-066 done

Layered settings with safe floors, an explainer for every value, and branding that can't break contrast.

• Workspace, department and profile layers; nothing can go looser than the platform floor
• Why this value: see where each setting comes from
• Accent colour with contrast-safe shades derived automatically; your logo in the sidebar
• Rename terms (for example Request to Ticket) across the UI and email

Tracker: BPMS-027 done

Every admin list is the same data grid: quick search, typed filters, multi-sort, saved views and exports that match what you see.

• Filter builder with AND/OR groups and a plain-language summary
• Saved views shared with a role, restored from a deep link
• CSV (formula-safe) and XLSX exports, audited

Tracker: BPMS-028 done

A ranked list of what needs attention, with compact activity numbers. Every number drills into a pre-filtered list with the same count.

• Overdue acknowledgements, admins without two-step verification, documents past review
• Acknowledgement and publishing activity, by department

Tracker: BPMS-063 done