Skip to content

Projects ​

Everything in Index Insure belongs to a project. A project is the workspace for a single insurance deployment: a pilot, a country, or a client engagement. This page explains why the product is organised this way and what it means in practice.

What a project is ​

A project is a self-contained space holding its own areas, data, analyses, pricing, team, and audit trail. Index Insure is multi-project: many projects can run on the same platform at once, completely isolated from one another. A user can belong to several projects, but works in one active project at a time.

The active project drives everything ​

Whatever you do, you are doing it inside the active project. The lists you see, the data you can open, and the things you can create all belong to that one project.

You select a project  →  everything you see and do is scoped to it

Switch projects and the whole workspace changes: different areas, different data, a different book of cover.

Why isolate by project ​

  • Confidentiality. One client's or country's data is never visible from another project.
  • Independence. Each project can have its own areas, data sources, products, and team without affecting the others.
  • Clean operations. The same platform can host many pilots and live projects side by side.

Access is per project ​

Your role and what you can do are granted within a project, so your abilities can differ between projects: you might administer one and only view another. Membership in a project is the first gate: without it, you cannot see that project's data at all.

Choosing and switching projects ​

  • A project switcher at the top of the screen shows the active project and lets you change it.
  • Your profile lists every project you belong to and which is your default.
  • If you belong to no project, the platform guides you to ask an administrator for an invite.

Why it matters across the journey ​

Every step of the journey is project-scoped: a data source registered in one project is invisible in another, an analysis only covers its own project's areas, and audit entries are recorded against the project they happened in. When something "isn't showing up," the first question is almost always: which project is active?

Where to go next ​