Organisations

Overview

An organisation is the tenant. Normally it represents the Private Equity relationship: the firm, and everything it has on the platform.

Beneath it sit funds and projects — and beneath projects, companies and shareholders (A1.2). An organisation is the boundary within which all of that lives.

Only a Super Admin creates organisations. And an important separation: Super Admin status does not by itself grant access to customer data. A Super Admin who needs it must be deliberately added as an Org Admin of that organisation.

What you'll learn

• What an organisation is and what sits beneath it

• The three fields it takes, and which one to think about

• Why Org Admin is the most consequential grant on the platform

• The order in which a new organisation is set up

Creating one

Three fields:

Name — the firm's name, as the team will recognise it.

Domain Name — required, and unique across the platform. The format is constrained: letters, numbers and hyphens only, no spaces.

Description — free text.

The domain name matters more than it looks

Two reasons to choose it deliberately.

It is unique and it identifies the organisation. Being a constrained, unique string, it behaves as the organisation's stable identifier rather than as a label.

It appears to relate to who can register. The platform carries an error stating that only email addresses from authorised domains can be used to register, which suggests an organisation's domain governs which email addresses can self-register into it.

So set it from the firm's actual domain rather than an abbreviation, and set it correctly first time. It is not a field to revise casually.

Org Admins

An organisation needs at least one Org Admin — the role that creates projects within it and has access to every project beneath it (A1.4).

Inviting one takes an email address. The platform tells you if that person already holds the role.

Because Org Admin reaches every project in the organisation, including ones that do not exist yet, it is the most consequential grant on the platform. Give it deliberately and to few people (C1.3).

The order of setup

1. Super Admin creates the organisation — name, domain name, description.

2. Super Admin invites the first Org Admin.

3. The Org Admin creates projects (C1.2).

4. Project Admins and Editors do the work within them (A2.3).

Each step hands off to the next, and the handoff is deliberate: platform administration and customer data are separate responsibilities.

Common problems

The domain name is taken. It must be unique platform-wide. Confirm you are not creating a duplicate organisation for a firm that already exists.

The domain name is rejected. Letters, numbers and hyphens only. No spaces, no dots.

A Super Admin cannot see a customer's data. Correct, and intentional. They must be added as an Org Admin of that organisation.

Someone is already an Org Admin. The invite tells you. Nothing to do.

Related

• C1.2 — Creating projects in an organisation · the next step

• C1.3 — Managing organisation-level access · granting and removing reach

• A1.2 — How Kapitable is organised · the same model from the deal team's side

• A1.4 — Roles and what each can see · the role hierarchy in full