Layerpath

Description Features Permissions Security & Compliance

Talk to Layerpath right in Slack. Share screenshots, a screen recording, or a Loom or YouTube link, and describe what you want to explain. Layerpath turns it into an interactive walkthrough: a step-by-step explanation people can click through, with callouts and voiceover, ready to review and share.Keep the conversation going to shape it. Say "make this easier for a new customer," "shorten the steps," or "translate it to Spanish." You can make these changes without opening the editor. Create, refine, and share from the same thread, whether you're preparing onboarding, documenting a process, or answering a teammate's question.How it works
1. Mention @Layerpath with your screens in a channel or thread it's been added to, or send it a direct message.
2. Watch your walkthrough build in the thread. Loom and YouTube videos can be up to 10 minutes.
3. Reply in the thread to edit walkthroughs created in Slack. Try "blur the customer names," "shorten the steps," or "undo that." Walkthroughs created in the Layerpath app are edited there.
4. Click the card to open its details beside the conversation. Select Open tour to play it in your browser, Make video for a narrated version, or share the link. When the walkthrough changes, its cards update and the link stays the same.What you can ask for
Shorten steps or change their tone. Translate steps, callouts, and voiceover into 34 languages. Add or rewrite the voiceover. Blur names and email addresses. Move, merge, or remove steps. Get a narrated video, a written guide, or embed code. Say "show my tours" to see your recent walkthroughs.Built for your team
An Owner or Admin of your Layerpath workspace connects it once. Each Slack workspace connects to one Layerpath workspace. Then full members of your Slack workspace can create walkthroughs and edit the ones they have access to, including ones requested by teammates. Walkthroughs are saved in your Layerpath workspace and use your Brand memory for your logo, colors, and tone, when it's set up. Owners, Admins, and Editors in Layerpath can open them in the editor.Guests and people from other companies in shared channels can't ask Layerpath to create or edit walkthroughs in your workspace. They can see walkthrough cards posted in shared channels, and anyone with a published walkthrough link can open it.What Layerpath reads
When you mention Layerpath, it reads the messages and files in that thread to respond to your request. In channels, it only works where it has been added. You can also message it directly.Get started
Connect your workspace at https://app.layerpath.com/slack/install, then add Layerpath to a channel with /invite @Layerpath. New to Layerpath? Start free at https://app.layerpath.com/signup.Walkthroughs made in Slack are free until December 31, 2026, under our fair use policy. See plans at https://www.layerpath.com/pricing.Layerpath uses generative AI and can make mistakes. Review walkthroughs before you share them. Slack's AI agent panel needs a paid Slack plan. You can still mention @Layerpath in channels and threads on free Slack plans.Questions? Email support@layerpath.com.

Layerpath will be able to view:

Layerpath will be able to do:

Review the details to better understand this app’s security practices. To learn more about assessing apps for your workspace visit our Help Center.

General

Privacy & data governance

Data retention policy

Walkthroughs, and the text, screenshots, and recordings someone asks Layerpath to use, stay in the connected Layerpath workspace until they're deleted. Copies of files sent through Slack are kept for 7 days. Copies made while downloading a Loom or YouTube video are kept for 1 day. Records of requests (which action, which walkthrough, when, and whether it worked, not message text) are kept for 90 days. Slack thread memory is deleted 30 days after the last message in the thread, and within 7 days after the app is removed. Details: https://www.layerpath.com/privacy

Data archiving and removal policy

Deleting a walkthrough in Layerpath stops its share link within a few minutes. To erase every copy of its files, or to delete integration data or an account, customers email support@layerpath.com, and we delete within 30 days. Backups of a deleted account are gone within 3 months. Removing Layerpath from Slack deletes its bot token right away and its Slack thread memory within 7 days. It doesn't delete walkthroughs already made, which stay in the customer's Layerpath workspace until deleted.

Data storage policy

Customer data is stored in the United States. Our database runs on Supabase and our files are in Amazon S3, both encrypted at rest with AES-256. Walkthroughs, and the screenshots, recordings, and text someone asks Layerpath to use, are stored in the connected Layerpath workspace. For Slack, Layerpath keeps short-lived context only for threads it's working in; other channel messages are dropped and not stored. Slack bot tokens are encrypted a second time with AES-256-GCM under a separate key and are never written to logs.

Data center location(s)

United States

Data hosting details

Cloud hosted on Amazon Web Services, Supabase, and Vercel in the United States.

Data hosting company

Amazon Web Services, Supabase, Vercel

App/service has sub-processors

yes

Guidelines for sub-processors

https://www.layerpath.com/security

App/service uses large language models (LLM)

yes

LLM model(s) used

Anthropic Claude via Amazon Bedrock; Google Gemini via Vertex AI and the Gemini API; OpenAI API. Speech to text: Deepgram, with OpenAI as fallback. Voiceover: ElevenLabs and OpenAI voices.

LLM retention settings

Slack data never trains or improves any model, whatever the customer's tier. Bedrock doesn't keep requests for the Claude models we use, Gemini data caching is off, OpenAI data sharing is off, and we've opted out of Deepgram's model improvement.

LLM data tenancy policy

Shared, provider-hosted models. Each Slack workspace connects to one Layerpath workspace, and its walkthroughs stay there. We don't run a model per customer or use one company's data for another.

LLM data residency policy

Data is stored in the United States. AI requests may be processed outside the US: Amazon Bedrock can route to any AWS region it supports, and Google may process requests in any country with its facilities.

Certifications & compliance

Security