Use functions, scripts, and script triggers to enhance security

Use FileMaker functions, scripts, and script triggers to enhance security for common tasks such as deleting, auditing, and maintaining records. For example, use scripts to:

• add or delete accounts, reset account passwords, change passwords, enable or disable accounts (for FileMaker file accounts only)

• re-log in as a different user (for FileMaker file accounts, the Guest account, and external server accounts only)

• archive records when you don't want a user to delete records

• provide information about the user's current session and state for regulatory compliance and auditing

• provide custom messages when security limitations affect the user

Important  Do not use functions, scripts, or script triggers to replace FileMaker security features.

Notes 

• By default, scripts run using the privilege set of the account that is currently signed in. This can cause issues if the script tries to perform an action the user does not have the privileges to do. Test all scripts across all privilege sets to protect the integrity of your data.

• When using script steps to communicate with systems outside the FileMaker Platform, choose available options that interact via SSL encryption. For example, the Insert from URL script step includes the Verify SSL Certificates option, and the Send Mail script step allows communication with SMTP servers that use SSL encryption.

• Use functions to get information about the current user, such as Get(AccountName), Get(AccountGroupName), and Get(AccountType). For example, use the Get(AccountExtendedPrivileges) function to test whether a user has a specific extended privilege.

See "Functions reference," "Script steps reference," and "Script triggers reference" in FileMaker Pro Help.