The security file must follow the following file definition.

It can have a different name and Owner than this definition, but the file structure must be identical as it is used by the BSec Classes.

You can even use a variable for the owners name in your app.

A txd is provided to import into your dictionary for the file definition. See includes.

BSec uses Logical labeling with the  Procedure Name, EIP, action name, and/or button name for the procedures and controls in question.  This is used for the S Item Field in the Security File and should not be changed.  This Field, and the Key on it, are used by the BSec Class to do the lookups.  The other three fields are readily user accessible and can be changed to provide the security levels, more meaningful end user category and descriptions,  as well as having additional sort orders added to the end user's local browses, etc.   They are filled by Jumpstart with the procedure category and procedure Description for starters.