Turn incoming requests into work with a home.
Bring your project closer to the tools your team already knows.
Give the request a project, then give the work an owner.
Hi team,
I placed an order this morning. Could you help me update the delivery address?
Thanks,
Alex
I placed an order this morning. Could you help me update the delivery address?
Request received through the project inboxActivity stays with the issue
Example workflow. Configure a project email address and choose who triages new requests.
Email and website feedback today. GitHub and Slack connections in development.
A request, a piece of feedback, a development update. Each connection should make the next step clearer—and keep the people doing the work in the loop.
Create a project email address and bring incoming requests into the work. Keep the queue close to the team responsible for following through.
For self-hosted deployments, configure the mail provider and domain for your instance.Embed a small support form on your website. Route submissions into a project so feedback becomes something the team can act on.
Choose the issue type, adjust the form, and add the generated embed to your website.The planned GitHub workflow connects repositories, issue references, and pull request activity. Follow a piece of work from the original issue into development.
Repository connections are in development. Authorization and synchronization are not yet available in the web app.The planned Slack connection brings project updates into team channels. Keep relevant activity beside the conversations that help your team move forward.
External app connections are in development. Slack setup will appear as the connection becomes available.Start with a request source your team already uses. Give it a destination, make the behavior clear, and follow the first request all the way through.
Pick the project that should receive the request. Decide who owns the incoming queue and what the next step should be.
Set up a project email address or configure your website widget. Choose the details that make a submission useful to your team.
Send a representative request. Check its content and visibility, confirm the right team can find it, and build from there.
A useful connection has a clear destination. A useful queue has someone looking after it.
Bring compatible AI clients into the same project context through leera’s MCP server. Connect with scoped access and keep the workspace at the center of the work.
Explore the MCP serverCompatible clients · Scoped workspace access
04 / The practical details
GitHub connection setup in the web app is in development. The planned workflow links development activity to issues, with transitions based on configured rules and status mappings. The examples on this page preview that workflow; they do not connect a repository.
Start with the connections that remove a specific handoff in your workflow. Give each incoming queue an owner and check that the integration creates useful context before adding more sources.
Give the conversations and requests around your project a place to become progress.
