For your staff

What it asks of your people. And what it never records.

Most of the questions that stop a rollout are not about features. They are about whether the people on the floor can actually get in, and what is being kept about them. Both answers are on this page, and both are checkable.

This page exists to be forwarded. If you are being asked to approve a rollout, the section you want is What it does not record.

Getting in without a work emailWhat it does not record

Sample code and card from a demonstration workspace. Real codes are issued one per named worker and can only be used once.

Every plan, including the cheapest

Nobody is left out for not having a work email.

Workers without a company email can join a workspace by entering an admin-issued access code and their phone number, which is confirmed by a one-time SMS code.

  • In their own languageTranslate a post or a Knowledge Hub article into any of ten languages on every plan: English, French, Arabic, German, Spanish, Portuguese, Dutch, Swahili, Mandarin and Hindi.
  • Where they already lookNotifications reach people in three places on every plan: an in-app centre, push to mobile via Firebase Cloud Messaging, and email. Each notification type has a fixed priority that decides which channels fire, so urgent broadcasts push and email while reactions and new posts stay in-app.
  • They can find each otherEvery workspace gets an employee directory on every plan: each person has a profile with photo, bio, job title, department and who they report to, searchable by name.
  • One tap to confirmWhen something has to be read, it says so and it stays at the top until it is done. Confirming is a single button. If the admin attached a couple of questions, they come first, and until they are passed the confirmation is not recorded.

Codes are issued one per named worker and are single-use. This is not one shared code for a device, a shift, or a site. The SMS is a Firebase phone-verification code sent only to confirm the worker owns the number; Kayden never sends posts, announcements, or notifications by SMS. Verification SMS are capped per workspace per month.

The part a works council asks about

What it does not record.

Every line here is a fact about how the software is built, not a promise about how it will be used. Each one is stated the same way on the specification page.

  • It does not track readingThere is no view count and no read receipt anywhere in the product. The only thing recorded is a deliberate confirmation: a person choosing to press a button. Nobody can see how long someone looked at something, or whether they opened it at all.
  • An anonymous survey is anonymousA pulse survey can be marked anonymous, in which case the server stores no respondent identity with the answers. A separate record notes only that a person answered, never what they said, which is how a second submission is refused and non-responders can still be reminded without anybody knowing how they replied.
  • One text message, everThe one-time code that confirms a phone number is the only text message the product will send. Nothing else is delivered that way: announcements, policies and reminders all arrive inside the app.
  • The directory finds people, not facts about themSearch matches display name only, not job title, department or email, so it finds a person you can already name rather than answering 'who runs payroll?'.
  • Moderation is automatic, and a person decidesEvery post's text and images are checked automatically against Google's safety classifiers, and anything flagged is routed to an admin moderation queue. The check runs immediately after a post is published rather than before it appears, and it fails open: if the classifier is unavailable the post is treated as approved.

Show it to the people who would have to use it.

That is usually the fastest way to find out whether it fits how you actually work.