Creating Kiosk solutions (FileMaker Pro Advanced)
For your solution to display in Kiosk mode, you must:
 •
create an account with a limited privilege set or create a specific Kiosk account.
 •
clear the default option of logging into the file with the Admin account.
 •
enable Kiosk mode. At the same time that you enable Kiosk mode, you can bind the database as a runtime solution.
Note  Kiosk mode is ignored if the solution is opened by accounts with the Full Access privilege set, a privilege set that allows management of extended privileges, or a privilege set that allows modification of layouts, value lists, and scripts.
To create a limited access Kiosk account:
1.
With the database solution open, choose File menu > Manage > Security.
2.
In the Manage Security dialog box, click New.
3.
In the Edit Account dialog box, type an account name, click Active for the Account Status, and select New Privilege Set from the Privilege Set list.
4.
In the Edit Privilege Set dialog box, give the privilege set a name and description.
5.
For Layouts, Value Lists, and Scripts, select either All view only or All no access.
6.
Clear the Manage extended privileges checkbox.
7.
Select other options as required.
8.
Click OK.
To enable Kiosk mode:
1.
Close all database files that you are going to customize.
2.
Choose Tools menu > Developer Utilities.
3.
If you have used the Developer Utilities on the same database solution before and saved your settings, click Load Settings.
4.
Click Add to locate the files that you want to customize.
5.
If you add multiple files, double-click a file in the list to specify the primary file.
6.
Select Developer Utilities settings as required. See Setting up files for developer solutions (FileMaker Pro Advanced).
7.
For Solution Options, click Specify.
8.
In the Specify Solution Options dialog box, select Enable Kiosk mode for non-admin accounts.
9.
Select other options as required. See Specifying options for developer solutions (FileMaker Pro Advanced).
10.
Click OK.
11.
You can quickly repeat this process by clicking Save Settings and choosing a folder and location for your settings file. See Saving solution settings (FileMaker Pro Advanced).
12.
Click Create.
If you did not bind the files to a runtime application, the Developer Utilities copy the selected database files to the Project Folder. If you did bind the files to a runtime application, the Developer Utilities copy all of the runtime files to a new folder created inside the Project Folder and named after the runtime solution.
To change the default option of logging into the file with the Admin account:
1.
With the database solution open, choose File menu > File Options.
2.
In the Open tab, clear Log in using.
3.
Click OK.
Notes
 •
If there is no Quit or Exit button available in your Kiosk solution, users must force-quit the application by pressing Alt+F4 (Windows). With OS X, users can exit a solution running in Kiosk mode by pressing F9 or F11 to access another open application window. Force quitting is not recommended because it can cause data corruption or damage open files.
 •
To ensure that users can access the primary file and quit the application cleanly:
 •
In each auxiliary file, provide a startup script that opens the primary file.
 •
In each auxiliary file, place a Main Menu button that runs the startup script to open the primary file.
 •
In the primary file, include an Exit button.
 •
For information about creating buttons and scripts that emulate missing menu options and window controls, see Using scripts and buttons to control Kiosk solutions (FileMaker Pro Advanced).
Related topics 
Displaying databases in Kiosk mode (FileMaker Pro Advanced)
About creating runtime solutions (FileMaker Pro Advanced)
Using scripts and buttons to control Kiosk solutions (FileMaker Pro Advanced)
Creating dynamic buttons (FileMaker Pro Advanced)
Was this topic helpful? Send feedback.