Access Settings

Configuration of access to your application and events

Application Access Settings

Decide who can access your event in the Meeting Application System. It's up to you whether users should log in when entering the Mobile App and Landing Page, or have open access to the content.

NOTE!
The MA system includes modules that, due to their specificity, require logging in, and these are: Feedwall, Attendees, Treasure Hunt, Business Matching. There are also modules that have functions requiring logging in, e.g. Surveys and Quizzes, asking questions in the Agenda or adding photos in the Event Gallery.

To protect the event from unwanted guests, you can optionally create an additional access code for the event, or restrict access to a completely closed guest list using the Whitelist function. By using these methods, the content in the App will be 100% confidential.

Types of Access to the Application

In the second step of creating an event in the Admin Panel in the Access section, you must choose one of four types of access for users (it can be changed later):

White List

  • This is a type of access where the organizer defines a list of specific event attendees. Only people whose email address has been added to the MA System in the Admin Panel under the Manage, in the Users module can join the event. You can learn how to import users from the article Import Users. Additionally, you can specify an entire domain of email addresses whose members will be granted access. If a user outside the White List wants to join the event, they appear on the participant list with the status Pending. The MA System Administrator must approve such a person in the Admin Panel under the Manage, in the Users, module before they gain access to the event content.

Disabled

  • Any user can join the event without the need to log in. The application will suggest logging in only when the user selects a function of the application for which it is necessary.

Optional

  • A user intending to join the event will be prompted to log in, but they can skip this step by clicking “x” in the upper left corner of the screen. Logging into the Mobile App and on the Landing Page is possible using Facebook, LinkedIn, an Apple account, or a previously created account in the MA System. If there is no account, you can proceed to user registration, located at the very bottom of the screen.

Required

  • The MA System requires every user to log in. Logging into the Mobile Application is possible via Facebook, LinkedIn, Apple account, or a previously created account in the MA System. If there is no account, you can proceed to user registration, located at the very bottom of the screen.

NOTE!

When setting the access type to Disabled, the default module that opens automatically upon entering the event, so-called First to open, cannot be one of those modules that require logging in. In the panel, in step four Summary, the selection of such a module is blocked by graying it out.

Modules requiring login are: Feedwall, Attendees, Treasure Hunt, Business Matching.

Access Code to the Application

If you want to secure the event from guests outside your organization, you can set an additional access code that the MA System will request when trying to join the event. This feature is completely independent of the type of access you choose, so you can apply it to each of them:

The access code should consist of a string of characters or digits and cannot contain spaces or diacritical marks such as: ą, ę, ó, ź.

Remember to provide the Access Code to the target users before they start joining the event!

Attention! When the event is not yet published, access to it is limited to a maximum of 5 participants. Even if access is set to Disabled, they will still need to log in so the system can record these 5 people.

Have a successful event with Meeting Application!

Did this answer your question?
😞
😐
😁