# Lassu documentation
> Quickstarts for sharing a screen walkthrough, replacing a status meeting with an async update, and collecting browser-recorded video responses on a website.
Public references: [recording buttons](https://lassu.ai/docs/recording-buttons), [API and webhooks](https://lassu.ai/docs/api), [MCP](https://lassu.ai/mcp), and [pricing](https://lassu.ai/pricing.md).
## Send a client a walkthrough
1. Create a Lassu account and choose a workspace. [Download the Mac or Windows app or Chrome extension](https://lassu.ai/download).
2. Open the site, design, report, or product you want to explain. Record the screen with your voice, adding your camera if useful.
3. Show the relevant change, explain why it matters, and finish with the decision or next step you need. Trim the start and end if needed.
4. Choose who can watch. Anyone-with-the-link access allows browser viewing without a Lassu account. Workspace-only and restricted access apply audience checks.
5. Send the video link in email, client chat, or project messages. Viewers can revisit the explanation and use timestamped comments to keep feedback in context.
A useful daily client update follows: what changed, what is ready to review, and what you need next. A website handover can show the actual editing and publishing steps. A marketing update can explain an existing dashboard; Lassu does not generate the marketing report itself.
For Fiverr or Upwork clients, follow the platform's rules for sharing links. See [freelancer workflows](https://lassu.ai/use-cases/freelancers).
## Give a remote team an async update
Record progress, decisions, blockers, and the next action while the work is on screen. Share the link in the existing team chat, along with relevant task or file links. Teammates can watch with subtitles and respond during their own working hours.
For a time-zone handoff, show the current state, explain what you have tried, and identify where the next person should start. For an async standup, keep the update focused on what others need to know. Use a live conversation when the issue needs immediate discussion.
With the workspace's Slack integration connected, public Lassu videos play inside Slack. Private and restricted videos open in Lassu for access checks. In other chats the video link opens in a browser. Viewers do not need to install the recording app.
See [remote team workflows](https://lassu.ai/use-cases/remote-teams).
## Add a video recording button to a website
Recording buttons collect **camera and microphone** video on desktop or phone. They do not record a visitor's screen. Applicants or customers do not need a Lassu account or installed app.
### Create and embed the button
1. As a workspace administrator, open **Workspace → Recording buttons** in Lassu and create a button.
2. Add the website addresses where it may appear. Choose the response identity mode and recording duration. Buttons allow 1–60 minutes, with a maximum of 10 minutes on Free.
3. Open **Add to website**. Copy the Code embed or give the **Integrate with AI** prompt to your coding agent.
4. Paste the embed beside the application question, survey prompt, or testimonial request. Replace `YOUR_BUTTON_ID` below with the actual button ID.
```html
```
The website or form builder must allow custom HTML and scripts. The standard embed does not require writing the recorder yourself. A site builder that blocks scripts cannot use this snippet directly.
Visitors allow camera and microphone access, record, review and trim, then submit. Responses appear under **Received videos** and on the workspace’s **Videos** page. Try a submission from an allowed page before making the button available to visitors.
### Choose who can record
- **Anonymous:** visitors can record without confirming an email. They can manage their response until they close the page.
- **Email verification:** visitors confirm their email with a six-digit code. They can return through email to review, trim, replace, or delete their video without a Lassu account.
- **Your website's signed-in users:** your server supplies a short-lived signed identity token. This needs a server-side integration and is not a paste-only setup.
For existing-login identity, use the guide's HS256 token format with workspace ID as issuer, button ID as audience, a stable user ID as subject, and a five-minute expiration. Keep the signing key on your server. Refresh the token when the widget requests identity again.
### Match a response to an application or survey item
Optional embed attributes let you set a stable submission key, attach details, and choose a theme:
```html
```
A submission key identifies an item for the person recording; it is not a password or proof of identity. Metadata is a flat JSON object with up to 32 fields, 64 characters per field name, 512 characters per value, and 8 KiB total. Use a signed identity integration for trusted account details.
The JavaScript SDK supports mounting, updating, and destroying the widget in an application. Client events include `submitted`, `ready`, `updated`, `deleted`, `error`, and `identity-required`. A browser event is not authoritative proof of a submission; verify it with the server API or a signed webhook before changing a business record.
### Connect responses to your own system
The production API base is `https://api.lassu.ai/v1/api`. Workspace administrators create a read-only or full-access API key; send it as a Bearer token from your server.
- `GET /received-videos`: list responses, with filters such as button ID, submission key, and received date.
- `GET /received-videos/:id`: retrieve a received response. Its received-video ID stays stable when the visitor replaces the take; the underlying video ID can change.
- `GET /recording-buttons`: list the workspace's buttons. Full-access keys also support creating and updating buttons.
- `GET /videos` and `GET /videos/:id`: retrieve workspace videos and available content such as summaries, chapters, and transcripts.
- Webhooks include `receivedVideo.ready` and `receivedVideo.deleted`, along with video events. Use a ready event when your workflow needs a playable response.
Verify the `Lassu-Signature` against the raw request body using the webhook secret and HMAC-SHA256. Check the timestamp and handle duplicate events by event ID. Keep API keys and webhook secrets out of browser code. See the [API reference](https://lassu.ai/docs/api) for exact request schemas, permissions, signature verification, pagination, rate limits, and retries.
### Troubleshooting an embed
- A disabled button can mean the current website address is not allowed. Check the button's website list and state.
- The page must allow the supplied script and recorder frame in its Content Security Policy, and permit camera and microphone use.
- Visitors must grant device access. Where offered, **Record in a new window** provides a fallback to the embedded recorder.
- Review both the button duration and the workspace's plan limits. Pro's unlimited screen recording time does not remove the recording button's 60-minute maximum.
See the [full recording-button guide](https://lassu.ai/docs/recording-buttons) for browser requirements and integration examples.
## Let a local AI coding agent capture a demo
Lassu exposes local capture tools through MCP for compatible clients such as Codex, Claude Code, and Cursor. Install and sign in to Lassu on the same computer as the client, enable AI access, and grant the required screen, camera, or microphone permissions. Follow the [MCP setup page](https://lassu.ai/mcp) to connect the client and workflow skills.
The tools can help capture a feature walkthrough or daily update. Check the running app's capabilities: supported Mac builds offer narration and advanced screenshot editing; Windows supports basic capture and recording. A hosted chat does not gain access to your desktop merely from a shared video URL.
## Access, plans, and further reading
- [Pricing](https://lassu.ai/pricing.md): workspace quotas, paid Member and free Member Lite roles, and program benefits.
- [Selection guide](https://lassu.ai/compare.md): screen walkthroughs versus responses, text updates, and live calls.
- [Privacy](https://lassu.ai/privacy) and [terms](https://lassu.ai/terms): service and data-handling information.