Luwawaluwawa

Work and connections

See what your team is working on without asking.

Tickets from Linear, pull requests from GitHub and Slack activity sit next to a person's leave, pay and equipment. People can file leave, approve it, claim expenses and answer check-ins from Slack.

Start freeBook a demo
nkhata.luwawa.app/people/limbani-zulu/work
LZ

Limbani Zulu

Software Developer · Operations
OverviewEmploymentLeaveEquipmentWorkDocuments

Tickets

L
OPS-41 Route planner exportLinear · assigned
In progress
L
OPS-37 Fuel report totals wrongLinear · assigned
Done

Pull requests

G
#214 Fix fuel report totalsGitHub · opened
Merged
G
#216 Depot list sortingGitHub · opened
Open

Conversations

S
#field-ops14 posts this week
Today
S
#dev6 posts this week
Fri

Public channels only. Metadata on the record, not message text.

The Work tab on an employee record.

An engineer at her desk between tasks

GitHub

Pull requests opened and merged.

Install the GitHub app and choose which repositories it covers, private ones included. Each person's pull requests, opened and merged, appear on their record and in their own workspace.

Reviews given are not collected.

G
#214 Fix fuel report totalsOpened · 3 files
Merged
G
#216 Depot list sortingOpened
Open
G
#209 Depot listOpened · 5 files
Merged

Linear

The tickets someone is actually on.

Linear issues assigned to a person show with their current state, so a manager can see the work without asking for a status update.

L
OPS-41 Route planner exportAssigned
In progress
L
OPS-44 Driver sign-off screenAssigned
Todo
L
OPS-37 Fuel report totals wrongAssigned
Done

Slack

Public channels in. Reminders and actions out.

Luwawa reads public channels only, never private channels or the contents of direct messages, and keeps metadata on the person's record: which channel, and when.

It can send people a direct message, such as a reminder or a check-in prompt. From Slack, people can file leave, approve it, open an expense form and answer a check-in.

How the Slack app works

What it reads

  • Public channels, and who belongs to them
  • That a person posted in a public channel, and when
  • Member names and emails, to match people to records

What it does in Slack

  • /luwawa leave to file leave, and leave approval
  • An expense form, and check-in answers in a Slack form
  • Direct messages: reminders and check-in prompts

What it never reads

  • Private channels and the contents of direct messages
  • Message text on a person's record. Metadata only.

Setting it up

Settings, then Integrations.

An owner, admin or IT admin connects each tool from inside Luwawa. Slack only reads channels the app has been invited to. People are matched by email, and anything ambiguous is left for you to confirm.

1
Open Settings, then IntegrationsGitHub, Linear and Slack sit side by side
2
Connect and authoriseEach tool shows exactly what is asked for
3
Invite the app to public channels/invite @Luwawa
4
Match accounts to peopleBy email. Never guessed.

Not yet

What Work and connections does not do today.

  • GitHub reviews given are not collected. Only pull requests opened and merged.
  • GitHub, Linear and Slack only. No Jira, GitLab, Teams or Google Workspace.
  • Activity is shown as it happened. It is never turned into a score or a ranking.

One place to run your company.

Create a workspace