ManualHow-to guidesEncryption
Give an integration access to encrypted data
If your tenant encrypts, an integration sees the names of participants through the API only as pseudonyms. So that it reads the names, confirm its key by comparing emojis with the person who runs the integration.
Prerequisites
- Account type Super admin, with access to the encrypted data.
- The integration's service account has the roles Admin and Participants (Settings: Service accounts).
- The integration has registered its key: Encryption shows Key waiting for confirmation. How the integration does this is described in fepli developers.
- The person who runs the integration is on the phone or next to you.
Steps
- Select Settings > Integrations and open the service account.
- Under Encryption, select at Share with it what the integration is to read: All participants or Children of {organizer profile}.
- Select Compare emojis and ask the person to let the integration start its side of the comparison.
- Read the 7 emojis out to each other and compare picture and order.
- If all match, select They match. If one differs, select They don't match.
beispiel.fepli.eu/admin/einstellungen/integrationen/api/service-accounts/…
AnmeldeportalRead and write
Encryption
Key waiting for confirmationWaitingRegistered on 14.03.2027. Nothing is encrypted for it before the emoji comparison.
FingerprintF6F0 F48E D485 AF87 5737 9FBEKey ID3f0c2c1e-8a4b-4c5d-9e6f-7a8b9c0d1e2f
Share with itAll participantsCompare emojis
Revoke key …
Compare emojis
Do these emojis match the ones the integration “Anmeldeportal” shows, in the same order?
- 🦋Butterfly
- 🔑Key
- 🚲Bicycle
- 🍕Pizza
- 🌙Moon
- 🎸Guitar
- ⚓Anchor
They don't matchThey match
The Encryption section of the service account and the comparison with the integration.
Result
The dialog shows ““Anmeldeportal” is confirmed. An unlocked browser of the team shares the records with it in the background.”, and the section shows Key confirmed. The log of the data subject rights records Integration key granted.
If it does not work
| Problem | Remedy |
|---|---|
| The section shows No key of its own. | The integration has not registered a key yet. The person who runs it does that first. |
| “Waiting for the integration …” does not go away. | The integration has not started its side of the comparison yet. Keep the dialog open until it does. |
| After the comparison, the integration still reads only pseudonyms. | An unlocked browser of the team shares the keys of the records in the background. Sign in and unlock, and they arrive. |
| The integration is to read nothing any more. | Under Encryption, select Revoke key and confirm. A new key needs a new comparison. |