Entity Contacts
Contacts are people saved on an entity, each with a name and an optional email address. They are the recipients Strise offers when you send a form or request an identity verification, so an address is entered once rather than on every request.
Contacts are available to every team and need no module or feature toggle.
Where You Find Them
Contacts appear in two places on both company and private person entity pages, and both offer the same actions:
| Location | Purpose |
|---|---|
| Overview tab → Contacts card | The primary place contacts are managed |
| Data collection tab → Forms card | The same list, beside the forms it feeds |
What a Contact Holds
| Field | Notes |
|---|---|
| Name | Required. Up to 200 characters. |
| Optional, but must be a valid address when given. Up to 320 characters. | |
| Primary | At most one primary per entity, marked with a Primary badge. |
Contacts are listed with the primary first, then oldest first.
Managing Contacts
Add contact opens a dialog for the name and email. The first contact saved on an entity becomes the primary automatically.
Each row's ⋮ menu offers:
| Action | Notes |
|---|---|
| Edit | Change the name or email. |
| Make primary | Promotes this contact and demotes the previous primary. Hidden on the primary itself. |
| Delete | Removes the contact. Forms already sent to them are unaffected. |
Everyone on the team can see contacts. Adding, editing and deleting them requires permission to manage contacts — without it the Add contact button is hidden and the row menu is disabled. Ask a team manager if you need it.
How Contacts Are Used
Sending a form
In the Send form dialog the recipient is a dropdown of saved contacts, shown as
Name · email. The primary contact is preselected. Choosing Someone else lets you type an
address by hand; when that address isn't already a saved contact, the dialog offers to save it as
one.
Identity verification
An IDV request needs an email address for the person being verified, and Strise holds none — a saved contact linked to that person supplies it. Contacts created through the IDV flow are linked to the person they belong to, which is how the address is found again on the next request.
Scope
Contacts belong to one team and one entity. They are not shared between teams, and they are not part of the entity's registry data — nothing you save here is published, screened, or sent to a provider. A contact is not a role, a shareholder or a beneficial owner; saving someone as a contact makes no claim about their relationship to the entity.
Related
- Customer Facing Forms — send KYC forms, declarations and questionnaires.
- Identity Verification — confirm the identity of the people behind a company.
- Data Collection — the tab that gathers documents, forms and IDV.
Last updated on