About these help pages

These help pages are Placepoint's official user documentation, a single reference to look things up in while you work. Large parts are generated automatically from Placepoint Fusion and from the sources we collect data from. That gives broad coverage, but automation has its weaknesses. Here we explain how the pages are made, and how you can tell us if something is wrong.

How these pages are built

The pages are built with Docusaurus from Markdown files maintained by the Placepoint team. Every change rebuilds everything and publishes it to docs.placepoint.no. There is no full-time editorial team, so updates happen continuously, much of it automatically.

Screenshots

The screenshots are captured automatically by Playwright: a script logs in to Placepoint Fusion, navigates through all the panels and takes the images along the way.

Where the information comes from

The content is stitched together from several sources: feature descriptions and examples are written by the team based on the running app; the FAQ is a curated collection of questions we are often asked; short how-to answers behind the green i icon at the bottom right in Placepoint cover the same features; the Glossary explains more than 300 terms from property, planning and construction, enriched with links to Lovdata, Kartverket and other authoritative sources; Data and sources gives you the opposite entry point, listing the datasets Placepoint combines, who supplies them and where you can find them directly at the source. When a source is updated, we fetch it again and rebuild the pages.

Search

The search field at the top of every page indexes the whole documentation, including the Glossary, Data and sources and the FAQ. Search for feature names ("map layer", "matching"), technical terms ("UFA", "matrikkel") or whole questions. This is often the fastest route if you know what you are looking for, but not where it is described.

What might be wrong

Most of these pages are made by AI agents that actually use Placepoint Fusion: they log in, click through the app, take screenshots along the way and learn the features bit by bit, with a little help from us. That means the documentation should in principle "never" lag behind the product, but also that some kinds of errors can slip in:

• Screenshots taken at a slightly odd place on the map compared with what they are meant to show.
• Screenshots that have failed, for example where a map layer did not finish loading before the image was taken.
• Text that is slightly off the mark and needs a human polish.
• Terms or fields imported from external sources with small errors that have not been caught yet.
• Links that point to a page a data source has moved.

Tell us when you spot something. We are very happy to receive feedback. Every message helps us pick up genuine errors quickly and prioritise correctly what the next round should improve.

Help us improve

Feedback is the fastest way these pages get better. We would particularly like to hear what is missing or should be better documented: tell us if you are looking for something and cannot find it, if an example would have made a feature easier to understand, or if you have a workflow we have not covered. We are happy to receive requests for both basic examples ("how do I find the owner of a property?") and advanced ones ("how do I combine matching, monitoring and demographic search into a portfolio candidate pipeline?"). Good examples are one of the most requested things we have.

Three channels for feedback, from the shortest to the most detailed:

• "Did you find what you were looking for?", the button at the bottom of every single help page. One click is enough; a comment with it is gold. We read every single piece of feedback and use it actively to prioritise what to improve in the next round.
• The chat bubble at the bottom right goes straight to the Placepoint team. Use it for short observations. Staffed during working hours.
• Email to support@placepoint.no is good when you want to write a bit more or attach screenshots.

If you mention the URL of the page in question, we will find it quickly.

Placepoint v1, Placepoint Maps (Newsec Maps) and PropCloud

We also have user documentation for three other Placepoint surfaces:

• Placepoint v1, the predecessor to Placepoint Fusion, still running at console.placepoint.no.
• PropCloud, search in properties, companies and ownership, area analysis and project folders at app.propcloud.no.
• Placepoint Maps, maps, property data and analysis tools at app.newsecmaps.com.

Feedback and requests about these three sets are received in the same way as here: the chat bubble or support@placepoint.no.

Experiments

We have made a few small data-driven experiments, more or less finished. We also have an MCP server that makes Placepoint's data and functionality available in Claude.