Skip to main content

Knowledge Base

Operational guidance that reduces support load and improves adoption.

The Blocora knowledge base is designed to explain the operating model clearly, support SEO with real topics, and answer practical user questions around leasing, payments, renewals, notices, security, owner access, and tenant self-service.

Search-friendly structureReal operator questionsFR/EN-ready article modelSupport deflection + product trust

Knowledge search

Find practical answers by workflow, not by docs jargon.

4 results

Public content rules

Public routes must stay FR/EN-ready in structure, metadata, and future content modeling.
Every page must have a clear conversion job and a clear SEO topic focus.
Marketing copy must stay product-specific, operational, and free of generic SaaS filler.
Portal pages must explain scope honestly: simpler than the admin app, safer by design, and permission-bounded.
Use one strong page topic and one strong CTA per primary public page.
Keep metadata specific to the workflow or audience on the route.
Use FAQ schema on pricing and article schema on knowledge-base articles when the content supports it.
Avoid duplicate public routes that compete for the same intent.

Categories

The knowledge base is structured around product jobs, not generic docs buckets.

Getting started

Planned

Operator onboarding, workspace setup, and public-product orientation.

Open category

Properties and units

Planned

Portfolio structure, occupancy, documents, and unit record continuity.

Open category

Leasing workflow

1 live

Listings, leads, visits, applications, and lease handoff guidance.

Open category

Applications and screening

Planned

Review expectations, request-info flow, and approval discipline.

Open category

Leases and signatures

Planned

Draft creation, packet continuity, and activation readiness.

Open category

Payments and receipts

1 live

Ledger clarity, payment posting, receipts, and arrears follow-through.

Open category

Renewals and notices

1 live

Deadline control, notice proof, and resident response handling.

Open category

Tasks and team

Planned

Dashboard, task ownership, and operational coordination patterns.

Open category

Owner portal

Planned

Read-mostly owner visibility, statement access, and scope boundaries.

Open category

Tenant portal

Planned

Payments, documents, requests, and resident self-service guidance.

Open category

Security and permissions

1 live

Organization scope, least privilege, and audit-aware workflows.

Open category

Integrations

Planned

Provider dependencies, rollout checkpoints, and partner add-on guidance.

Open category

Troubleshooting

Planned

Operational fixes, common blockers, and support deflection articles.

Open category

Article rules

One real operator question should map to one article.
Use direct titles, practical steps, and product screenshots where they add clarity.
Call out permission boundaries, workflow risk, and the next operator action when relevant.
Keep article structure FR/EN-ready even when the first public publication is in English.

Leasing operations

Run vacancy to lease as one operating path.

A practical operating playbook for taking one vacant unit through listing, lead intake, visits, application review, lease creation, and activation without handoff gaps.

Listing to lead continuity
Visit and application handoff
Lease activation readiness
Read article

Renewals and notices

Control renewals, notices, and proof without side spreadsheets.

How to keep renewal cycles, notice deadlines, delivery proof, and resident responses inside one governed operating path instead of scattered documents and inbox checks.

Deadline visibility
Notice proof tracking
Resident response continuity
Read article

Accounting and payments

Create collections visibility without building full ERP accounting.

A practical guide to making due, paid, overdue, and receipted activity obvious for operators while intentionally deferring full accounting depth.

Ledger clarity
Receipt continuity
Collections follow-through
Read article

Jurisdiction design

Scale province-aware operations without forking the product.

Why Blocora uses one shared jurisdiction layer for templates, rulesets, deadlines, and wording rather than separate product branches by province.

Shared ruleset layer
Template version control
QC / ON / BC / AB rollout logic
Read article

Ready to try the workflow?

Use the knowledge base to learn Blocora, then create your own demo workspace.

Blocora's knowledge base is meant to make setup self-serve. Start a free demo account when you want to test the product, and use contact only for migration, Custom, or portfolio-fit questions.