Integrations

Luwawa for Slack

See what someone actually worked on, on the same record that holds their leave, pay and equipment. Public channels only, and never the words anyone wrote.

What it reads

Metadata, and only from places everyone can already see.

Channels
Which public channels exist, and who belongs to them.
Activity
That a person posted in a public channel, and when. A count and a timestamp.
Members
Names and email addresses of workspace members, to match Slack accounts to employee records.

What it never touches

The permissions for these are not requested at all.

Unreachable by construction rather than filtered after the fact. There is no setting that turns any of this on, and no write access of any kind: the app cannot post, rename anything, or invite anyone.

Message text
Not requested, not stored, not displayed. Ever.
Private conversations
Private channels, group messages and direct messages.
Files
Anything uploaded to Slack, including attachments and images.

Connecting it

Five minutes, and it starts inside Luwawa.

Connecting begins in your account rather than here, because a Slack workspace has to be attached to a company.

  1. Step 1

    Sign in to Luwawa

    You need to be an owner, an admin or an IT admin. HR admins read the results but do not connect the workspace.

  2. Step 2

    Open Settings, then Integrations

    Slack sits alongside GitHub and Linear. Select Connect.

  3. Step 3

    Authorise in Slack

    Slack shows exactly which permissions are being asked for. Approve, and you are returned to Luwawa.

  4. Step 4

    Invite the app to the channels that should count

    Type /invite @Luwawa in each public channel you want reflected. Channels it has not been invited to are not read at all.

  5. Step 5

    Match Slack accounts to people

    Most match automatically on email address. Anything ambiguous is left for you to confirm, never guessed.

Good to know

The dull questions, answered before you ask them.

Several workspaces
A company can connect more than one. Someone active in two of them is still one person on one record.
Disconnecting
Removes the stored tokens immediately and stops all reading. Activity already on a record stays until you delete it.
If someone leaves
The connection belongs to the company, not to whoever set it up, so it keeps working when they go.
Cost
Included in every Luwawa plan. There is no separate charge for the integration.

Available today: activity on employee records, as described above. Filing expenses and leave from Slack, and approving them without leaving Slack, are being built. The /luwawa command is registered but replies with a link to the dashboard until they ship.