fepli
ManualReferenceSystem and data protectionAdmins

Service accounts

When another program is to work through fepli's interface, such as a registration portal of your municipality, it needs access of its own. fepli calls this access a Service account.

Super admins find these accesses under Settings > Integrations. The interface itself is switched on by the app API. How a program is connected is shown in the tutorial Connect the API.


Creating and managing an access

An access belongs to no person. Like a team account it has roles, and it has one or more keys with which the program signs in.

ElementEffect
PageIn the app API, Manage service accounts also leads here.
AccessEvery access has a page of its own with its keys and actions.
New service accountCreates an access, with Name, Description, Roles and Access.
RolesAdmin, Super admin, Participants, Payments, Organizers; at least one, Admin is preselected. Participants and Payments also need Admin or Super admin.
AccessRead only or Read and write, Read only is preselected. With Read only, no key of the access may write either.
New API tokenA key for the program, with Label, Valid until and Access. Without a date it never expires. fepli shows it only once.
ActionsEdit, Disable and Enable, Revoke per key, Delete under Delete service account
Disabledfepli rejects the keys of the access. New keys can be created only after Enable.
DeletedThe access and all its keys are deleted. Programs lose access immediately.
Names in the historyIf a program changes offers, registrations or receipts, the history shows “{name} (service account)” with the name it had then. If it creates a registration, it counts as created by the team.
Organizers’ declarationA program cannot confirm the declaration. If the season requires it, fepli rejects the program's invitations to new organizers.

Encrypted data

For an instance with encryption, a program sees participants' names only as pseudonyms, that is as substitute names of 4 characters. It reads the real names only with a key of its own that a super admin confirms.

For this, the page of an access with the role Participants shows the section Encryption. How the program registers its key is described in fepli developers.

ElementEffect
StatusPseudonyms only: the program has no key of its own. Waiting: the key is registered but not yet confirmed. Active: the key is confirmed.
FingerprintIdentifier of the key the program signs with, in 6 blocks
Key IDIdentifier the program chose for its key
Share with itAll participants or Children of {organizer profile}. Once the key is confirmed, Reads and Confirmed by with the name of the super admin appear there.
Compare emojisStarts the comparison. Whoever looks after the program starts its side there at the same time. Both check that the same emojis appear in the same order.
Revoke keyThe program loses access to every name at once. What it has read so far it may keep. A new key needs a new comparison.
  • Until the emoji comparison, fepli encrypts nothing for the key.
  • Once it is confirmed, an unlocked browser of the team shares new records with it in the background.
  • Delete on the access revokes the key as well.
  • The log of the data subject rights records Integration key granted and Integration key revoked.

The steps are described under Give an integration access to encrypted data.


Messages

MessageMeaning
“Participants and Payments require the role Admin. Pick Admin as well.”Select Admin or Super admin as well as Participants or Payments.
“The service account is disabled.”The program cannot sign in until you select Enable.