Skip to content
EN
How to

Users and access: show who decided

For: The administratorTakes 5 min.Last updated

Short answer

Under Settings > Users and access, add a user with a name and a role and press "Invite". The user opens the link and creates a passkey on their own phone or computer. Once there are users with a passkey, GoalCube requires a passkey for decisions, so the identity comes from the passkey and not from a name someone types in.

Try it

Walkthrough: Add a userStep 1 of 4Fictitious data

Enter the user's name.

All steps (4)
  1. Enter the user's name.
  2. Choose the role. It decides which cases the user may decide.
  3. Press "Add user".
  4. The user has been created. The next step is to register a passkey on the user's own device.

Invite, and create the passkey

What it looks like: Users and passkeysFictitious data

Press Invite next to the user and send the link, for example in Teams. The user opens the link on their own phone or computer, presses Create my access and confirms with Face ID, fingerprint or PIN. The link can only be used once and expires after 72 hours. Only an administrator can invite. See Create an account, log in and invite colleagues.

If the user is sitting next to you, you can also press Create passkey here on the user's own device. The passkey stays on the device; GoalCube stores only a public key.

Users and access is included in the Personal data + People decisions plan. See Plans.

What does it change?

  • Once there are users with a passkey, decisions must be confirmed with a passkey. This is the "passkey" recommendation in the rule library.
  • The audit log shows the user's ID and role instead of initials.
  • If an access is not used for 90 days, Tasks asks whether to keep or remove it.
  • With roles switched on, users can only decide cases in their own area.

If you log in with a passkey, the person who is logged in is always the one named on a confirmation or decision; the initials field disappears.

Screens recorded from GoalCube 0.26.0 on 22 October 2026 with fictitious data.

Read next

All articles in Prove: People decisions