Plateforme/PWA - API Config

To access the configuration, simply click on the API tab

Domaine

The first settings are the domain settings
Here you will find your domain for your English and/or French site.

You can also link "system mails" directly from this tab:The first settings are the domain settings Here you will find your domain for your English and/or French site. You can also link "system mails" directly from this tab:

  • Password reset mail: automatic mail sent when a participant clicks on "forgot password" on the platform
  • Activation mail: mail sent to participants for their 1st connection to the platform. This mail is used to create the password
Mails

You must first have created the e-mails in the mailing section to be able to link them here.

Domaine

Your project manager is responsible for setting up the domain in the APIs.

Other languages

If your platform is in a language other than French or English, you won't see the associated domain here and won't be able to link password reset / activation emails
Get in touch with your project manager!

Code PIN & PWA

Code PIN

When your app is encapsulated in the AppCraft "Your event in the pocket" application, you need to define a PIN that allows participants to access your app's login page.

This is where you define it. It can contain letters, numbers, upper case, lower case...

PWA

This section lets you configure the elements of the progressive webapp
The progressive webapp lets you add your site to the mobile home screen like an application, without having to download it from the stores.

  • Start_url: domain of your event
  • Scope: slug of your app's home page, usually "/"
  • Short_name & Name: name displayed on the phone under the PWA image when added to the home screen
  • Theme color: main color of your event
  • Background color: color that will be displayed, on android, when launching the PWA before arriving on the login (during the short loading instant)
  • Icon: image that will be displayed on your home screen to access the PWA. Format: 512x512px

 

Setting up the PWA
Contact your project manager to set up the PWA. He or she will need to make a number of other settings to make it work

Notifications

Here you can add the icon that will be displayed on the phone when you receive a notification about the PWA.

Notifications

To guarantee the deliverability of notifications, especially on iOS, the PWA must be encapsulated in the AppCraft Your event in the pocket application.

Authentication 

The authentication section is used to define the type of password used to connect participants to the platform/PWA.

Connection possible for

Allows you to filter which participants have the right to connect to the application/platform

Different types of password

User password

Each participant defines their own password
To do this, they receive an e-mail with a button that redirects them to the creation of their password
Once this has been created, they are logged in
In the event of a forgotten password, they can send themselves a password reset e-mail via the login page and the "forgotten password" button.

User password

This is the most secure connection method

Default password

The default password is used to define a generic password, the same for all
On 1st login, participants must log in with their e-mail address and this password
Once logged in, a pop-up window opens so they can choose their own password
If they forget their password, they can send themselves a password reset e-mail via the login page and the "forgotten password" button.

Enter the desired default password in the box below the password type drop-down list.

Same password for all

The password is the same for all, and the participant cannot change it, nor send a password reset e-mail to himself.

Enter the desired password in the box below the password type drop-down list.

One-time password

This connection mode is recommended only if no sensitive or personal content is accessible on your platform/PWA.

One-time password

The one-time password is used to send each participant a unique password by e-mail.
This password is used to log in once, and must then be changed by the participant.
The password then expires.

One-time password

To set up the one-time password, you need to create an e-mail template with the {password} variable inside, which will generate a password for each participant.
Don't hesitate to contact your project manager for testing purposes.

Login via SSO

Connection via SSO is also possible. Please contact your project manager for details
This option is not included in the standard package.

SEO Robot.txt

The SEO Robto.txt button activates SEO on browsers, once the SEO has been set up on the platform/PWA.

Contact form

This section lets you define the e-mail address to which e-mails from the contact form integrated into the platform will be sent, and the e-mail template.

  • Contact email: email to receive emails from participants using the platform's contact form
  • Email template: email template to be received at the contact email address defined above
  • Authorize public access: if your platform is semi-open and the contact page is accessible without logging in, check this box to allow non-logged-in people to use the form.

Contact form

For this to work, you first need to add the "contact" block to one of your pages on the
platform. For the e-mail template, ask your project manager to set the right variables in the template.

Participants

On your platform, you can integrate a "who is who" page with the list of participants
On this page, you can display certain participant data
For RGPD reasons, you must first make public the fields you wish to display on this page.

  • Participants to be displayed: define the participants to be displayed on the who is who page. For example, you can exclude test accounts or admins, not display VIPs...
  • Public list of participants: checkbox to define the fields to be authorized
  • Public fields for participants: here you'll find all the columns present in participants. You can define public fields, which can then be displayed on the who is who page.

Participating fields to be displayed

Once your fields have been made public, go to the who-is-who page to choose which fields to display.

Forced platform closure

Before opening your platform, or after closing it, you can force the platform to be closed so that participants cannot access it
However, you can set a password so that certain participants (admins, for example) can access it and view the content.

  • Forced closure: check box to force closure
  • Unlock password: password to access
  • Authorized users: here you can select which of all participants are authorized to access the site.

Accès après fermeture

Rapprochez-vous de votre chef de projet pour obtenir le lien avec le mot de passe défini forcé à l'intérieur et ainsi accéder à la plateforme
Si votre plateforme est semi-ouverte, demandez à votre chef de projet de vous expliquer comment fermer les pages non soumises à connexion

Social wall

You can blacklist words and/or emojis on the social wall
Posts from participants who try to publish a message containing a blacklisted word/emoji will not be displayed on the social wall.

Enter your words & emojis here, one below the other

Gamification

The gamification block allows you to activate gamification on your platform, if this is part of the project.

  • Activate: enables you to activate it
  • Make gamification available to: allows you to filter which participants have access to it and which don't
  • Automatic notification closing time: every time you unlock a badge, it is displayed for a few seconds on the right-hand side of the platform. You can set the display time here, in seconds.

Gamification

Once gamification has been activated, you need to set up all your badges in the gamification tab of the backoffice.