Practice Lattice for Slack

Direct-message pilot

The pilot answers source-backed Practice Operations questions only in a one-to-one direct message with the Practice Lattice Slack app. It does not read or answer channel messages, private-channel messages, group direct messages, files, reactions, or email addresses. App Home may show setup, safety, and availability information.

Who may connect and use it

A currently authorized client administrator may connect one Slack workspace for the exact client organization and accept the versioned terms shown during connection. Use is limited to eligible internal, full Slack members who remain authorized for that client. Practice Lattice rechecks the workspace, member, client access, allowance, and current source-library authorization for each request and again before an answer is sent. Access may be blocked, paused, or disconnected for security, entitlement, support, or legal reasons.

Your instructions and responsibilities

You authorize Practice Lattice to process the direct-message question and a bounded window of up to 15 messages from that Slack thread to provide the requested answer. Keep Slack and Practice Lattice accounts secure, review answers and citations before relying on them, and use the integration only for lawful business purposes. Do not submit protected health information, patient-identifying information, client secrets that are not approved for this service, or content you are not authorized to use.

Information processed

Slack provides stable app, workspace, member, direct-message, event, and message identifiers plus the live direct-message text needed for the current request. Practice Lattice may fetch live Slack member and direct-message details to verify identity and eligibility. The question, bounded thread context, and generated answer are processed by Practice Lattice and its approved AI provider for that interaction. Slack and the AI provider process information under their respective terms and policies.

What Practice Lattice retains

Practice Lattice does not save Slack message bodies, thread text, prompts, generated Slack answers, Slack files, profile names, or email addresses in its application database. It retains limited workspace, member, event, message, installation, authorization, token-rotation, delivery, usage, denial, terms-acceptance, security, and audit metadata. A citation may retain a bounded, source-verified document excerpt and hash as access evidence; that excerpt comes from the cited Practice Lattice document, not from the Slack conversation.

Slack retains direct messages and app replies according to the connected workspace’s Slack plan, settings, exports, and retention rules. Practice Lattice retains its limited metadata and audit evidence for as long as reasonably needed to operate and secure the integration, resolve usage or access questions, meet contractual duties, and comply with law. A confirmed disconnect erases the stored encrypted Slack access and refresh credentials; required terms, security, and audit evidence may be retained.

Sources, answers, and availability

Answers are generated from the client’s currently approved Practice Lattice source library and may be incomplete or incorrect. The integration is an operational aid, not legal, medical, tax, or other professional advice. It does not replace review by an authorized person. Access depends on Slack, model, hosting, and source-library availability and is provided on an “as available” basis during the pilot.

Permissions and security

The pilot requests only the Slack bot permissions needed to send messages, read direct-message history and direct-message identity, and verify workspace members. Slack token rotation is required. No system can guarantee absolute security, and administrators should disconnect the app and contact Practice Lattice promptly if they suspect misuse.

Suspension, disconnect, and changes

An authorized client administrator may request disconnection in Practice Lattice. Slack administrators may also remove the app in Slack. We may change or end the pilot prospectively; a material terms change requires a newly versioned acceptance before a new connection. These integration terms supplement the accepted Practice Lattice platform agreement and the public Privacy Policy. If they conflict for this Slack integration, these more specific terms control to the extent permitted by law.