1 Reply Latest reply on Dec 10, 2014 2:59 PM by TSGal

    Security Setting

    bosch_bastiaan

      Summary

      Security Setting

      Product

      FileMaker Pro

      Version

      13 Advanced

      Operating system version

      MacOSX

      Description of the issue

      I wanted to create an user-account,
      where the (admin) user has FULL-Access-priveledges, Except changing security settings.

      Creating a new privelidge set, where user has equal setting to a FULL-Access-Admin, including access FMapp
      When logging in as that user, Unable to  make, Change and remove in all tables. See PNG's
      File>Manage database and other options are Greyed out.

      @t this moment it is NOT possible to make an Admin account that can do ALL, except changing security. (unless managed through server / external table ?)

      Steps to reproduce the problem

      create an account, where setting all equals the Admin-Full-Access, hence
      records-access and design
      records = make, Change and remove in all tables
      lay-outs ALL changeable
      Lists : ALL Changeable
      Scripts: ALL Changable
      Other privileges: ALL Marked "on"
      Available menu's ALL

      Expected result

      When having selected
      records = ALLOW  make, Change and remove in all tables,
      user must be able to make, Change and remove in all tables, / fields etc..

      Actual result

      User NOT able to access tables nor change field names (and other functions

      Exact text of any error message(s) that appear

      NO message

      Configuration information

      No relevant info

      Workaround

      No Workaround, except give user FULL Admin Access

      FM_Security_Bug_%3F.png

        • 1. Re: Security Setting
          TSGal

          Bastiaan Bosch:

          Thank you for your post.

          Creating a non-[Full Access] privilege set that limits the user to the database file is not possible.  However, if you have FileMaker Pro Advanced, you can then create a Custom Menu set that will not allow access to Security settings (and Custom Function and Custom Menus).  Then, when the new user opens the file, you can have a startup script compare the user's privilege name and load the appropriate custom menu.

          Let me know if you need additional clarification.

          TSGal
          FileMaker, Inc.