What is still missing from the batch review?
I’ll answer in Microsoft Teams using your linked Seal identity, so I only use records you can open in Seal.
Your permitted Seal records
Batch review response
- Records the review still needs
- References you can open in Seal
- Follow-up questions in the conversation
1What’s connected.
Chat with Neil in Microsoft Teams using your own Seal identity and permissions. Organisation setup guides administrators through app installation and Microsoft account linking.
Connection setup and permissions
Follow the guided setup in Settings → Integrations. Your workspace administrator may need to approve the app. Each person connects their own identity so Neil follows their Seal permissions.
Set up Microsoft Teams
- Open Settings → Integrations → Set up Microsoft Teams and download the Teams app package.
- Ask your Microsoft administrator to upload and allow the app in the Teams admin centre.
- Enter the Microsoft directory tenant ID where the app is installed, link your account, then open Neil and send a test question. Each user links their own account.
2Connect in Seal.
Sign in to Seal and open Settings → Integrations. An organisation admin can review the connection and complete the guided setup.
3Before it goes live.
Access and any write-back
Define which records are in scope and whose permissions apply. Whether the connection writes back at all is a separate decision, with its own mapping and approval.
Data and failure handling
Agree the field mapping, identifiers, units and source of record. Test missing or duplicate data, interrupted transfers and recovery before relying on the connection.
Verification and release
Review the configured connection for its intended use. Keep the requirements, checks and evidence with the change, and approve the release through your team’s controls.