NSECURED MemberGo / Use cases
Find the use case for your process
19 use cases in 7 themes. Pick a theme or type a keyword, then open a use case to see its data flow, roles and acceptance points. Examples use fictional data.
Collection and records
01New employee onboardingNew hires get a personal form link before day one. HR needs to know what has been submitted; finance needs the bank account only when setting up payroll.Integration design
Data involvedNational ID, payroll bank account, registered address, emergency contact
How it works
- HR starts a one-time collection from the onboarding flow; the new hire fills in the MemberGo page and sensitive fields go straight from the browser to the vault.
- The HR system’s onboarding list keeps tokens and completion status. Only fields that genuinely need checking show the last four digits.
- If an ID does not match, HR requests that field to verify onboarding data. After a second person approves, the authorized person may view it once within a time limit.
Business benefit
HR can chase missing items and finish onboarding, and the team inbox and onboarding spreadsheet no longer hold a plaintext copy.
Rollout and acceptance
Verify that reused and expired links fail. Confirm how emergency contacts entered on their behalf are informed. ID photos and passbook copies need separate document protection.
02Supplier bank-account changeAccounts payable receives a bank-change notice claiming to be from a supplier. Facing business email compromise (BEC), finance must confirm the sender and the new payee before changing payment instructions.Integration design
Data involvedSupplier bank account, account name, bank identifiers
How it works
- Procurement calls back using contact details already on file; the verified supplier representative updates the details on a dedicated collection page.
- The ERP holds the new token while keeping the old payment instruction. A second finance manager checks the call-back record, change form and account summary.
- Only after approval does the ERP switch to the new payee token; the first payment is checked against the active version and approval record.
Business benefit
Even if a clerk believes a fraudulent change request, independent confirmation and a second approver are two more points to stop it.
Rollout and acceptance
A test payment with an unapproved change must still use the old instruction. Payment release, bank file transfer and call-back procedures are run by finance.
03Shareholder register and dividendsA shareholder changes address while the share office prepares meeting notices, dividend payments and tax withholding. Each task needs different fields.Conditional
Data involvedShareholder ID number, mailing address, dividend bank account
How it works
- The share office verifies the shareholder and sends a collection page for self-update. Day to day, the register keeps shareholder numbers, tokens and necessary summaries.
- The office lists the fields each task needs: notices, payments and withholding. Sending a notice, for example, needs only mailing details.
- Producing a full register needs a separate flow in the share system: named recipients, a stated reason, a second approver and file handling after delivery.
Business benefit
Staff can prepare different tasks from the same shareholder data while everyday screens expose far less of the register.
Rollout and acceptance
The current disclosure API is single-field. Batch register export must be designed and accepted separately, recording version, scope and recipients.
04Candidates and external personnelAfter recruiting closes, the company still has consultant contracts and intern onboarding. Each record should follow its own purpose and retention period.Integration design
Data involvedCandidate contact details, consultant identifiers, passport number, residence permit number
How it works
- Collect fields as each stage needs them; for example, ask for ID numbers only once a hire is confirmed and onboarding starts.
- The recruiting system records each case’s closing date and retention basis. If the policy keeps unsuccessful candidates for six months, deletion is scheduled from the approved start date.
- Staff check due cases, results and the deletion ledger, and separately clean the talent pool and original CV files.
Business benefit
Different groups can have their own retention periods, and you can later show which data stopped being kept, when and why.
Rollout and acceptance
Six months is an example policy. Verify the closing-date start, retention exceptions and removal of external attachments. Document content protection is assessed separately.
Health and highly sensitive data
05Sick-leave certificates and health checksAn employee submits a sick-leave certificate. The scheduling manager only needs the leave dates; only staff handling a specific review need the restricted data.Conditional
Data involvedCertificate status, document index, necessary medical fields; sick-leave, health-check, occupational-injury or disability certificates
How it works
- First confirm the legal basis and necessary scope, and keep certificate status, restricted fields and original attachments apart.
- The leave request shows that a certificate is attached. To review a specific request, the handler applies for a single field and a different manager approves.
- Viewing a full report goes through the restricted document system’s permissions and logs, matching case number and access time.
Business benefit
Managers can handle attendance and HR can trace specific reviews, with different levels of access to medical information.
Rollout and acceptance
Document and large-object encryption is not yet implemented (architecture v3). A pilot first accepts fields, the document index and access control in the existing document system.
06Employee assistance and grievance casesAn employee files a harassment or bullying complaint and wants general HR and their manager unable to find the statement in everyday systems. If counselling is involved, who holds the original notes must be agreed in advance.Conditional
Data involvedContact details, case number, confidential statement index, external professional service contacts
How it works
- The case system creates a code name and a named handler list, and collects contact fields separately. Original counselling notes stay with the professional provider.
- Only named handlers may view necessary fields, citing the case. For review, an approver with no stake in the case is chosen.
- When a case is handed over, the previous handler’s access is revoked and who viewed what, why and when is kept. Testimony and attachments get their own viewing logs.
Business benefit
Investigations can change hands smoothly. Managers only get what they need to arrange work, and fewer people can reach sensitive statements.
Rollout and acceptance
Test cross-case reads and searches as a non-handler. Clarify each record’s legal nature, document protection and the external provider’s custody duties.
Tokenization and system integration
07Tokenizing core identifiersA company wants full ID and account numbers out of its ERP backups while keeping duplicate checks and master-data links.Core flow
Data involvedNational ID, passport number, bank account, field tokens and necessary summaries
How it works
- New values arrive through collection pages; the ERP references tokens and shows masks where needed. Migrating existing plaintext requires a separate hunt for copies.
- Types that need exact matching can use a keyed HMAC index inside the vault; secret types keep the index off.
- Payroll file production gets its own payroll-only delivery path with an agreed recipient, retention period and delivery record.
Business benefit
Business backups keep their links while full protected values stay in the vault. Other identifying clues still need review.
Rollout and acceptance
Check the ERP, exports and logs. Ordinary service accounts cannot disclose to people; payroll batch delivery is designed and accepted separately.
08One source of truth across group systemsAn employee updates their address in the HR system and other authorized systems; the company wants one correction to update every related process.Integration design
Data involvedIn-tenant subject reference, address field token, field version
How it works
- First confirm data ownership and tenant boundaries. Within one tenant, a controlled mapping links each system’s employee number to the same subject.
- The employee corrects the data on a collection page, the master system updates the active reference, and each system re-fetches the summaries its approved purpose allows.
- Verify that old tokens stop working, caches refresh and corrections are logged. Separate legal entities or tenants need their own lawful exchange process.
Business benefit
Address upkeep is centralized, staff can find which system still uses an old reference, and less is copied and synced by hand.
Rollout and acceptance
A shared host does not merge identities automatically. Accept same-tenant sync and test that another tenant cannot look up the same token.
09Separating test and productionEngineers need to reproduce onboarding or support flows and see masking and approval results in staging without copying production personal data.Integration design
Data involvedSynthetic data, test-tenant tokens, masked values, case status
How it works
- Create a separate test tenant, service accounts and credentials, run the full collection flow with fictional values and produce test-only tokens.
- Staging is blocked from the production vault; developers verify success, denial and expiry with synthetic cases.
- Confirm tokens from another tenant cannot be read, and spot-check test attachments, error reports and logs for production data.
Business benefit
Tests cover real permission branches, with less time spent hand-masking production data for testing.
Rollout and acceptance
Accept the test tenant, credentials, data sources and network egress. Free text or imported legacy data may still carry plaintext.
AI access and analytics
10Field access for AI assistantsAn internal AI assistant summarizes voucher processing. It needs document types and status, not ID numbers, bank accounts or passwords.Core flow
Data involvedVoucher status, personal-data tokens, model version, custom fields allowed for workloads
How it works
- The business system gives the assistant the status and tokens it needs. Secret and two-person types cannot be fetched by machines, and built-in personal data is never released to workloads.
- If VISCOR inference genuinely needs other data, create a machine-readable type; an enabled service account states purpose and model version on every request.
- MemberGo checks policy and records the request first, then the Key Broker unwraps authorized values field by field. A denial releases nothing.
Business benefit
The company can show which fields a model call received and on what basis, with model and run references kept.
Rollout and acceptance
Prompts, OCR source images, free text and uploads each need their own filtering. Hardware remote attestation is not yet complete (architecture v3).
11HR analytics datasetsAn HR analyst compares turnover and salary bands across job families. Report readers need trends, not identifiable employees.Integration design
Data involvedProject token, job family, salary band, start and leave month, group size
How it works
- The data owner approves the analysis purpose and period; records are linked with analysis-only tokens and names, IDs and detailed notes are removed.
- Analysts receive only approved fields. Exact amounts and dates become bands, and groups that are too small are merged.
- Before publishing, check whether department, title and period could identify someone, and delete analysis copies on schedule.
Business benefit
Teams can still compare groups, with a clear record of what was delivered and who may read it.
Rollout and acceptance
Tokenized data can still be re-identified. Analysis tokens, small-group thresholds and output checks must be built into the analysis process.
Data-subject rights and compliance
12Access, correction and deletion requestsA former employee asks to see their data, correct contact details and know what can be deleted. Staff need to explain the scope and outcome.Integration design
Data involvedIn-tenant subject reference, data types, purpose basis, deletion jobs and restore records
How it works
- The handling team verifies identity and tenant scope, compiles purposes, data types and external copies, and provides access or a copy as requested.
- Corrections update the active reference. For requests to stop collecting, processing, using or to delete, the responsible person confirms statutory retention and exceptions.
- Approved deletions are written to the deletion ledger before data is cleared. Restore drills replay the ledger and review the result, which feeds the reply.
Business benefit
Support can answer item by item: handled, retained by law, or needing follow-up in other systems.
Rollout and acceptance
Deletion records cover managed data. Ledger replay must complete after a restore. Check downstream copies and agree the format of replies and deletion evidence.
13Purpose limits and withdrawn consentAn employee agreed to event photos on the company website and later withdraws consent. HR must still run lawful everyday personnel administration.Integration design
Data involvedSubject reference, website publication purpose, consent version and time, withdrawal record
How it works
- Register website publication and personnel administration as separate purposes with their own legal bases; notice and consent keep matching versions.
- Publishing first checks the purpose and version are valid. After withdrawal, further use for that purpose stops and the web team takes down published photos.
- Check the website, caches and contracted channels; personnel work with its own legal basis continues as before.
Business benefit
An employee can withdraw one specific consent, and staff can explain what stopped and how the takedown is going.
Rollout and acceptance
Accept both the purpose check and downstream withdrawal sync. Original photos, media copies and takedown are handled by the systems concerned.
14Incident forensics and notification scopeA support account may have been misused. Security needs to know which requests were denied, which fields were actually disclosed and who may be affected.Integration design
Data involvedUser or service account, field references, stated reasons, times, request trace IDs
How it works
- Preserve vault records for the period first, then compare sign-in logs, business-system tickets, approvals and receiving-side events.
- Build the affected list from subject and field references, marking confirmed and open items, without copying plaintext into the investigation sheet.
- The responsible person assesses notification, who to report to and when under applicable law, keeping the basis and follow-up records.
Business benefit
Investigators can rebuild the sequence of access to managed data and give the evidence a notification decision needs.
Rollout and acceptance
In architecture v3, only each tenant’s successful workload usage events are guaranteed gap-free; other audit records are reconciled separately, and tenant audit export is still in development.
High-privilege secrets
15Break-glass access and rotationThe main administrator cannot sign in to the domain registrar, so the on-duty manager uses break-glass access to a backup admin account. The decision and who was responsible must be traceable.Conditional
Data involvedOrganization-held cloud and domain backup credentials, database emergency accounts, approved recovery shares
How it works
- Secrets are set with no index and cannot be sent to AI or connectors. The business system records custodian, asset number and token.
- The on-duty person requests single-field disclosure with an incident ticket; another person approves with recent MFA, and the authorized person sees it once within the time limit.
- The incident process notifies those responsible; after closure the password is changed or shares rotated at the source service, and custody records are updated and reviewed.
Business benefit
Emergency access has clear approval, use and clean-up duties, and exceptions can be reviewed afterwards.
Rollout and acceptance
Accept the disclosure page, notifications and rotation. Keep an independent recovery path in case the vault itself fails.
16Split custody of tokens and PINsFor corporate certificate signing, the person holding the hardware token and the person approving the PIN each have one duty.Conditional
Data involvedCorporate certificate PINs the organization may hold, server-room codes, token or safe identifiers
How it works
- Confirm the custody the issuer and holder allow, register the token number, and store PINs that may be held as restricted secrets.
- A named custodian signs out the token. After the approver checks the work order, the authorized user views the PIN for a limited time and completes the task.
- On return, sign-out, disclosure and signing times are compared. Loss or handover follows the issuer’s suspension or reset process.
Business benefit
Physical sign-out and digital disclosure each leave a record, so you can match each authorization to each signature.
Rollout and acceptance
Personal certificates and their PINs stay with the individual. Corporate e-banking activation codes follow the bank’s rules; verify physical and digital split custody.
17Offboarding review and account handoverIT is told an employee is leaving. After disabling sign-in, it must find which shared passwords they viewed and which external services they controlled.Conditional
Data involvedEmployee identity, account inventory, past disclosure events, asset owners, rotation status
How it works
- HR triggers the offboarding review; identity admins disable the identity, revoke active sessions and confirm the effective time.
- The governance platform’s offboarding flow lists handover and rotation items from disclosure history, account ownership and physical sign-outs.
- Asset owners change credentials at each source service and update stored values; a reviewer confirms old credentials no longer work before closing.
Business benefit
The handover list shows who changed and verified each credential, reducing what shared accounts let slip.
Rollout and acceptance
Verify suspension and old-credential failure with a test account. Tenant audit export, the offboarding list and source-system rotation need integration.
Members and customer service
18Member support and marketing consentA member calls to change their delivery address and stop promotional messages. Support must handle the two purposes and consents separately.Core flow
Data involvedMobile, address, birthday, member reference; ID number only where a task truly needs it
How it works
- Members enter their own details, with order notices, delivery and marketing recorded as separate purposes. Support verifies identity first, then checks the requested change against masked values.
- To view a restricted field, support gives a reason and gets approval under policy. Delivery receives only the name, phone and address a valid order authorizes.
- After marketing consent is withdrawn, further use stops, the marketing system excludes the member and the effective time is recorded.
Business benefit
The same member keeps getting authorized order service, and support can say exactly when promotions stopped.
Rollout and acceptance
Test that cross-member, cross-store and expired delivery authorizations are all denied. Marketing gives its own notice and records consent; existing lists and scheduled sends must honor withdrawal.
19High-privacy services and customer trustA blessing service handles family prayer requests. Staff must deliver the service, and members want to know who sees family details and for how long.Integration design
Data involvedRecipients, birth dates, family relationships; health data, if any, needs its own necessity and basis review
How it works
- Before collection, explain each purpose, necessity and retention period, confirm the basis for providing family members’ data, and offer optional fields.
- Members submit through a separate collection page; the order screen shows the service and tokens. Named staff may view details only when fulfilment needs it.
- After fulfilment, cases close under the retention policy; paper lists, on-site work sheets and contractor copies are cleared, and a rights request channel is offered.
Business benefit
The company can tell members exactly who holds which details, when anyone looks at them, and how to correct or delete them.
Rollout and acceptance
Use one mock order to check store, printing, notification and partner data flows. Public statements must match what is actually visible.
No matching use case. Try “account”, “employee” or another keyword.
Implementation types
- Core flow Uses field capabilities already described in the architecture.
- Integration design Needs configuration, approval steps or sync on the customer’s systems.
- Conditional Also depends on features in development, external systems or operating terms.
MemberGo helps record purposes, permissions and evidence of processing. Adopting companies must still confirm the legal basis for each field, the notices given, data-subject rights and notification duties, and how external recipients handle data they receive.
Choose the field first, then the integration
Start with one sensitive field that today travels by email, spreadsheet or business form. Complete collection, masking, disclosure and revocation first, then expand to other departments, attachments or automation.
