Relationship types
A relationship type is a link one counterparty can have to another — a director of a company, a guarantor for a borrower. Your organisation decides what the list holds.
Each relationship type has a host and one or more participants, and it reads differently from each end.
What a relationship type carries
| Field | What it is |
|---|---|
| Name | The stable identity everything else refers to. Fixed once you create it, and unique across your organisation. |
| Host label | How the host sees the link, such as “Guaranteed by”. |
| Inverse label | How a participant sees it, such as “Guarantor for”. |
| Host counterparty type | The type that owns the link. Set when you create it. |
| Participant types | The types that can stand on the other end. Set when you create it. |
| Liability basis | Whether a participant stands behind the host’s debts. |
| Active | Whether the type is offered when someone establishes a relationship. |
The name, host and participants are structural, so they are set when you create the type and fixed afterwards. The labels, liability basis and active state you can change.
Adding a relationship type
Creating a relationship type is staged from the start. Open the draft from the bar at the top of the screen before you add one.
- Go to Settings, then Relationship Types.
- Select New Relationship Type.
- Enter a Name, such as
Guarantee. - Enter the Host label and Inverse label.
- Choose the Host counterparty type and the Participant types.
- Choose the Liability basis.
- Select Create.
- Submit the draft from the bar to publish it.
The property schema
Open a type to see its Property Types — fields you capture on every relationship of that type. Add, edit and remove them on that panel. A property’s Kind and purpose roles are fixed once the property exists; its label and whether it is required you can change.
Marking a property required warns you how many existing relationships of this type do not carry it yet.
Liability basis
| Basis | What it means |
|---|---|
| None | The link records who is related, and derives nothing. |
| Joint and several | Each participant stands behind the host’s debts. |
Retiring a relationship type
Deactivate is the everyday choice. Clear Active on the type. It disappears from the establish screen, so nobody creates a new relationship of it. Relationships already established keep working.
Remove deletes the type. No other setting refers to a relationship type, so a remove is not blocked — use it for a type created by mistake.
What your organisation configures
Everything on this screen. The platform ships no relationship types of its own.
The host and participant types come from your counterparty types.