Finance | Project Operations, Human Resources, ...

Customer's Bank Account Number field hidden by security

(0) Share

Report

Posted on by ZvikaR

190

I noticed that if user does not have the "right" out of the box security roles, the [Bank Account Number] field on [Customer Bank] table becomes invisible.

Same thing for the equivalent form for vendors

Accounts Receivable > Customers > All Customers > [Bank Account] button

without enough security access:

with enough security access:

Is that a recent change to the out of the box security? I did not notice it previously.

How can I find out what out of the box security roles provide access to this field?

By trial and error I discovered that Accounts Receivable Manager and Accounts Payable Manager roles both provide access to this form/field. but how do I find all the rest?

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

André Arnaud de Cal... 304,711 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi Zvika,

This is caused by the Table Permissions Framework. If a table or field has the property 'AOS authorization' set to 'Yes' on the table design, then the fields or tables are considered to have sensitive data which needs additional permissions. On the standard privileges, you can see that permissions have been set on the tables and the fields.

To solve your question, you also need to add these fields separately on the (table) permissions node and set the access level. All other tables and fields will inherit the permissions from the menu item permissions.

Was this reply helpful? Yes No
Dan Budimir Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

I had a requirement in a lower environment where the users needed to see everything but not be able to modify it. I created a custom role and privilege, added the privilege to my role. Initially I added Read to all display menu items on the privilege, this then granted users access to all of the forms. But more needed to be done, using customer information as an example, you could not see bank accounts or financial dimensions, adding the Chief executive officer role as a sub role fixed that, now you could see bank accounts and financial dimensions. Even more was to be done, you could not see the the bank account number, this is considered highly sensitive. Adding the View sensitive customer bank account information privilege to my custom role fixed that, I really just added any privilege that started with View sensitive. I only had so much time to get this together, there may be a better combination or role/priviliege/duty, but this worked for me.

Was this reply helpful? Yes No
André Arnaud de Cal... 304,711 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Dan,

Thanks for sharing your experience. This indicates that the security should not be taken as a light task. Note that just adding any privileges to any role starting with View sensitive, will make the intended table permissions framework obsolete. Before doing that, you must understand the contents of these privileges. Also not all sensitive tables and fields are covered with privileges with this naming convention.

Recently, I wrote a blog about this topic: Securing a menu item is not enough - table permissions - Dynamicspedia

Was this reply helpful? Yes No