Private Persons
This guide covers common workflows for managing private persons in Strise Connect: searching for individuals, creating them, adding them to monitoring, and handling updates.
Search for a private person
You can search for private persons by national identifier or by name.
By national identifier
Use privatePersonIdentifierSearch to find a person by their official identifier (for example, SSN):
query FindPersonBySSN {
privatePersonIdentifierSearch(where: { identifiers: ["12345678901"], country: "NO" }) {
edges {
node {
id
name
}
}
}
}By name
Use privatePersonSearch to find persons by name. You can narrow results with optional filters:
query FindPersonByName {
privatePersonSearch(where: { query: "Ola Nordmann", country: "NO" }, pageInfo: { size: 10 }) {
edges {
node {
id
name
}
}
pageInfo {
totalSize
nextPageOffset
}
}
}Verify against official registries
Before creating a private person, you can verify their details against official registries using privatePersonRegistrySearch:
query VerifyPerson {
privatePersonRegistrySearch(where: { name: "Ola Nordmann", nin: "12345678901", country: "NO" }) {
name
identifier {
value
kind
}
birthDate
gender
address {
addressLine
city
zipCode
}
}
}This returns registry data that you can review before creating the person.
Create a private person
Use privatePersonCreate to create a person. This automatically enriches their data from registries:
mutation CreatePerson {
privatePersonCreate(where: { name: "Ola Nordmann", nin: "12345678901", country: "NO", address: [] }) {
success
person {
id
name
}
}
}If you want to skip registry enrichment (for example, after
verifying data with privatePersonRegistrySearch), use
privatePersonCreateNoEnrich
instead:
mutation CreatePersonNoEnrich {
privatePersonCreateNoEnrich(
where: {
name: "Ola Nordmann"
nin: "12345678901"
country: "NO"
birthDate: "1990-01-15"
gender: MALE
address: [{ addressLine: "Storgata 1", zipCode: "0001", city: "Oslo", country: "NO" }]
}
) {
success
person {
id
name
}
}
}Add a person to monitoring
Use privatePersonAddToMonitoring to start receiving alerts when changes are detected (for example, new PEP or sanction hits):
mutation MonitorPerson {
privatePersonAddToMonitoring(where: { id: "<person_id>" }) {
success
person {
id
name
}
}
}Fetch person details
Use the privatePerson query to retrieve full details including PEP, sanctions, and screening results:
query GetPersonDetails {
privatePerson(where: { id: "<person_id>" }) {
id
name
birthDate
gender
isMonitored
pepInfo {
pep
rca
}
sanctionInfo {
sanctioned
sanctions {
sanctionedBy
program
}
}
customRiskFields {
riskField {
id
name
}
selectedOptions {
id
name
}
}
}
}Update a person
Use privatePersonUpdate to modify a person's details. Only provide the fields you want to change:
mutation UpdatePerson {
privatePersonUpdate(
where: { id: "<person_id>", address: [{ addressLine: "Ny gate 5", zipCode: "0002", city: "Oslo", country: "NO" }] }
) {
success
person {
id
name
}
}
}Remove from monitoring
Use privatePersonRemoveFromMonitoring to stop Strise monitoring of a person:
mutation StopMonitoringPerson {
privatePersonRemoveFromMonitoring(where: { id: "<person_id>" }) {
success
}
}Removing a person from monitoring does not remove the person from Strise, and their register data keeps being updated. To stop register updates, unsubscribe the person. If you no longer need the person, for example when a customer relationship ends, delete them instead. See Private persons and population registers for how register updates work per country.
Stop register updates
Use
privatePersonUnsubscribe
to stop Strise from updating a person's data from their national population register. The person
stays stored. By default the person is also removed from monitoring; pass
removeFromMonitoring: false to keep them monitored:
mutation UnsubscribePerson {
privatePersonUnsubscribe(where: { id: "<person_id>" }, removeFromMonitoring: false) {
success
person {
registerSubscription {
status
unsubscribedAt
}
}
}
}Unsubscribing cannot be undone. Persons created with privatePersonCreateNoEnrich start out
unsubscribed. registerSubscription.status is SUBSCRIBED, UNSUBSCRIBED or UNAVAILABLE.
UNAVAILABLE means the person has no national identity number, their register has no ongoing
updates, or your team has no register access, and it takes precedence over UNSUBSCRIBED.
Delete a person
Use privatePersonDelete to permanently remove a person. Deleting also removes the person from monitoring and stops register updates:
mutation DeletePerson {
privatePersonDelete(where: { id: "<person_id>" }) {
success
}
}