Jump to content
Sign in to follow this  
nleon307

Tab Level Security

Recommended Posts

Is there a way to do tab level security other than to put a script on a tab to check security privileges?

Share this post


Link to post
Share on other sites

Tabs are part of the IUser Interface (UI), and the UI is not part of the security schema. You can control access to the data on a particular tab object through the Privilege Set attached to the active Account.

In FileMaker® Pro 12, it is possible to intercept the "click" when a user selects a tab object and in essence ignore or "eat" it. But I would not recommend this as a real security feature.

Steven

  • Like 1

Share this post


Link to post
Share on other sites

So with field level access, they would see "Not Authorized" (I cant remember exactly what it says) where the fields are they do not have access to, right?

If it's a lot of fields, mainly on specific tabs, is field level access usually used with the intercepted click or are different layouts used instead?

Share this post


Link to post
Share on other sites

There are two aspects to this: one is security and the other is user interface. The security aspect must be handled by denying access to the fields in the users' privilege set/s.

Then, if you like, you can prevent the users from seeing those fields by placing them in another tab panel or on another layout. My own preference would be to use tabs with 0 width borders, accessible by buttons only.

Share this post


Link to post
Share on other sites

So with field level access, they would see "Not Authorized"

Yes, unless you mask this at the UI level with conditional formatting.

Steven

Share this post


Link to post
Share on other sites

To elaborate on Stephen's point, you can set the conditional formatting to = not Get ( RecordAccess ) and set the font size to 500 px which would hide the "<No Access>" text.

You can apply conditional formatting to multiple fields / objects at once by selecting them all. And there are other ways of hiding the text besides the 500px trick.

Edit: This may not be an optimal solution if the field is set to allow user entry...the user will still get an error dialog, one that precedes onObjectEnter trigger.

Edited by David Jondreau

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Who Viewed the Topic

    1 member has viewed this topic:
    doughemi 
×

Important Information

By using this site, you agree to our Terms of Use.