FE Admin App

With the FE Admin App, you can manage the entire Fast Events plugin. Far-reaching possibilities to create and manage accounts and, for example, limit their functionality and only grant access to selected events.

The App has a responsive design. On phones it will use cards to display the information and bottom-navigation to navigate between Tools, Events and Orders. On larger screens, typically on phones in landscape mode and tablets in portrait mode, it will show multiple cards side by side and navigation will be in a sidebar.

On large screens, desktop browsers and tablets in landscape mode, the information is displayed in table format.

Install on Android or IOS

The App is available for Android 9.0 and above and IOS 15 and above.

FE Admin App ../_images/Admin-IOS.png

Install as PWA

If the Web interface has been installed, it is also possible to install the management interface as a PWA on any platform with a web browser. The URL is:

https://exampledomain.com/wp-content/uploads/fast-events/admin/

macOS

Browser

Steps

Safari

  1. Open the PWA URL.

  2. Click the Share button → Add to Dock.

Chrome/Edge

  1. Open the PWA URL.

  2. Click the Install FE Admin icon in the address bar

Windows

Browser

Steps

Edge

  1. Open the PWA URL.

  2. Click the icon in the address bar that says → App available. Install FE Admin.

Chrome

  1. Open the PWA URL.

  2. Click the icon the in address bar that says → Install FE Admin.

IOS

Browser

Steps

Safari

  1. Open the PWA URL.

  2. Click the Share button → Add to Home Screen.

Chrome

  1. Open the PWA URL.

  2. Click the Share button → Add to Home Screen.

Android

Browser

Steps

Chrome

  1. Open the PWA URL.

  2. Tap the ⋮ menu → Add to Home screen or Install FE Admin

Edge

  1. Open the PWA URL.

  2. Same flow as Chrome (both Chromium‑based).

ChromeBook

Browser

Steps

Chrome

  1. Open the PWA URL.

  2. Click the Install icon in the address bar.

Just configure a regular account and you are good to go.

While it is possible to switch between different accounts on the same server in the browser version of the app, it is not possible to switch between accounts on different servers. The WordPress REST API has a strict CORS setting by default for security reasons. By default, it is not allowed to use the REST API from a browser with pages loaded from another server. The easiest way is then to define multiple bookmarks that point to the correct server, or install different PWA’s. For example, if you have the Fast Events plugin running on 2 servers, configure the URLs as follows:

https://exampleserver-1.com/wp-content/uploads/fast-events/admin/
https://exampleserver-2.com/wp-content/uploads/fast-events/admin/

Nevertheless, for specialists versed in http header configurations and CORS, it is possible to access multiple servers from one location. However, we strongly advise against this.

Full list of capabilities

Depending on the permissions configuration, users will only see the components they are allowed to see. The full list of components is shown below. Permissions can be configured in the Permissions popupmenu choice in the Accounts tool.

Events

  1. Detailed overview.

  2. Synchronise parts of an event with another event.

  3. Detailed information about tickets sold.

  4. Detailed information on scanning tickets in progress.

  5. Basic settings.

  6. Show and modify email templates.

  7. Show, add, modify and delete input fields.

  8. Show and modify PDF templates.

  9. Show, add, modify and delete ticket types.

  10. Show, add, modify and delete scan keys.

  11. Show and modify seating plans.

  12. Show and modify tracking information.

  13. Show and modify Saas information.

  14. Add event.

  15. Duplicate event.

  16. Delete all orders.

  17. Delete event.

Orders

  1. Detailed overview of the order: it also requires displaying input fields permission.

  2. Email the order.

  3. Share tickets link.

  4. Share tickets PDF.

  5. Change the name, email address and custom status of the order.

  6. Refund and order.

  7. Delete an order.

  8. Delete tickets.

  9. Create tickets.

  10. Checkin tickets.

  11. Error log.

  12. Add new orders).

Tools

  1. Sales dashboard.

  2. Scan a ticket to see its details. This is an informational scan only. It also requires order details permission

  3. Show and delete logging entries.

  4. Maintain email lists / closed user groups.

  5. Show, add, modify and delete webhooks.

  6. Show, add, modify and delete coupons.

  7. Export orders to Excel format.

  8. Export tickets to Excel format.

  9. Export scans to Excel format.

  10. Show, add, modify and delete shortcodes.

  11. Export events.

  12. Import events.

  13. Send bulk order emails.

  14. Send bulk free format emails.

  15. Bulk refund orders.

  16. (Sub)account management.

Server accounts

The first time the App is launched, it will show the Server Account page where a new server can be configured. Press the + button to add a new server.

Administrator accounts

If the Web management interface is installed there is no reel need to use this type of account configuration. But of course, if you want to manage your events on the go, you can do that too. But bear in mind that ‘administrator’ accounts always have full access to all functionality. If full access is not needed, just configure a new regular account in the Accounts tool and limit its functionality.

To configure the ‘administrator’ account, enter any name, scan the qrcode on the Rest API settings page of the plugin and enter the login-name of the ‘administrator’ user in the ‘Username’ field.

For the application password, an application password needs to be created once in WordPress for the ‘administrator’ user. Make sure you are logged into WordPress as an ‘administrator’ user and choose Users -> Profile. Scroll down to the ‘Application Passwords’ section. Enter any name in New Application Password Name and press Add New Application Password. The popup window now displays the generated application password. Copy and save it and use it in this server configuration of the App.

Now that all fields are filled in, press save (disk icon at top right). To login click/tap the card shown.

Regular accounts

Create/maintain accounts in the Accounts tool of the Tools section. With the popupmenu choices you can configure all settings of the account.

Add/change account
  • Basic settings - tab

    1. Login: The login name of the account. This is only shown when creating an account. When the account is saved, a popup will show the application password. Be sure to save this in a safe location. You will not be able to retrieve it.

    2. Name: The descriptive name of the account.

    3. Emailadress: Use any emailaddress you want, even a non-existing one is ok. WordPress needs one, but Fast Events never uses it. Use a valid one if you want to use regular logins to WordPress for this account

    4. Disable WordPress login: The default is switched on. You can’t use the account to login to WordPress and a password reset wil not work either.

    5. Temporary blocking: If enabled, the account is temporary blocked. The user cannot use the App.

    6. Allowed endpoints: A comma separated list of allowed endpoints. The default value is fast-events/v1. But more can be added if there are other plugins using REST and if this user needs to be able to access those as well.

    7. Maximum number of sub-accounts: If this account is allowed - later in the Permissions settings - maintenance permission on its own account, specify here how many sub-accounts it can create. The sub-accounts all have the same set of permissions and events visibility as the account itself. But while defining it, you can narrow down the permissions even further. You can never extend them. If you want that, the ‘administrator’ first has to enable the extra permission on the account level.

  • Authorised events - tab

    Select the events the user has access to.

  • Saas - tab

    Only visible to ‘administrator` accounts and if Saas mode has been in enabled in the settings. It wil show if the user has already authorised the plugin to manage payment transactions on its behalve. If authorisation has been given the ‘administrator’ can revoke it.

Permissions

Select the permissions the account is allowed to use.

Copy/paste permissions

This copies or pasts all permissions.

Settings

It shows the configuration qrcode the user can scan to configure the account in the FE Admin App. Still the user has to manually enter the username and application password.

Reset API

If the API key is reset, then all users of this account and its sub-accounts must re-enter the API key.

Reset password

If the application password is reset, then all users of this account must re-enter the application password to continue using the App.

Sub-accounts

Maintaining sub-accounts more-or-less follows the same rules as maintaining an account. Except it uses the API key that is defined at the account level and it uses the same Basic settings as defined at the account level.

Delete account

Delete all information (including all sub-accounts!). Access to the App and the REST API is instantly disabled.

Once you have entered the server details, save them and click/tap the server card to log in. To switch between accounts, simply press the top-left ‘hamburger’ menu and select a different account.

Usage

The first time the App is launched and if Fast Events is running in SaaS mode and the sub-merchant has not yet authorized access to its payment information, a Connect with Mollie or Connect with Stripe screen will be displayed to authorise access.

The way the App works is pretty straightforward. You can use the buttons at the bottom or sidebar to switch between Orders, Events and Tools. As the App is responsive it either displays 1 or 2 cards side by side or information is shown in table format.

Pretty much every where you can double-tap on the content (card or line) to jump immediately to editing the content, provided you the permission to do so. For other choices you have to tap/click the three vertical dots and either a popupmenu or bottom-sheet will be shown.

How to use the different sections. Al examples are taken from the Web based version of the App. On other devices like phones or tablets it may look differently, but the same functionality is offered.

Settings

The App and Admin Web interface have some general settings. You can find them by clicking on the hamburger menu and selecting Settings. Most settings are related to sharing information within the application. For example, when sharing information with an email application, you can enter a subject and by default the text in the setting will be used.

Languages

The Language settings menu is located in the navigation drawer (top left icon).

FE Admin supports standard two languages: English and Dutch. You can add your own language by following the next steps:

  1. Make sure you have a Github account.

  2. Check the languages folder of https://github.com/fe-data/fe-admin-languages if your language is supported.

  3. If not, login with the Github account at https://gitlocalize.com/repo/9558 and check if the translation is in progress.

  4. If not, create a new issue in https://github.com/fe-data/fe-admin-languages/issues requesting the new language code. We will give you the role of moderator for the new language. Use the two letter codes from this source. Only LTR-languages are supported.

As a moderator you may receive review requests from other translators. Process them and when you are happy with the update create a pull request. Mind you:

  1. We will only process pull requests that originate from Gitlocalize, and will not process pull requests from private forks.

  2. For initial translations, we will only accept a full translation of the entire file. Partial translations will be rejected.

  3. Once the pull request has been processed, the new translation will be available in the app’s settings. Reload the translations and select the new language.

  4. There is only 1 moderator per language.

Use the Download languages button to download new languages or to update the current version, and then optionally choose another language. If you are asked to restart the app, make sure the app is completely removed from memory, then restart the app and optionally select a new language.

Events

Details

Share subject of a short overview of the event details.

Total sales

Share subject of an overview of the number of tickets sold.

Total scans

Share subject of an overview of the number of scans per location and ticket type.

Orders

Details

Share subject of a short overview of the order details, including the tickets.

Cache

If you switch between the order lists of different events, the order list is cached for this amount of minutes. You can always force to reload a fresh copy by pulling down the order list in the App or Web interface.

Tools

Error log

Share subject of an overview of a specific error.

Sales dashboard

Share subject of an overview of the number of tickets sold for the selected events.

Coupon email subject

The default subject used when sending an email with coupon information.

Coupon email body

Press the Set email body button to define the email body when sending an email with coupon information. This is the default body used when sending bulk coupon emails, but you can override the default by using the menu option to send the emails. The body can contain a number of keywords, that will be replaced with the information in the coupon.

  • {%EMAIL%} the email address in the coupon.

  • {%CODE%} the coupon code.

  • {%AMOUNT%} the discount percentage or amount.

  • {%START-DATE%} the coupon is valid from this date.

  • {%END-DATE%} the coupon is valid until this date.

  • {%MIN-TICKETS%} the minimum number of tickets required.

  • {%MAX-TICKETS%} the maximum number of tickets allowed.

  • {%MIN-AMOUNT%} the minimum amount required.

  • {%MAX-AMOUNT%} the maximum amount allowed.