Conditional Metadata Configuration Based on Logged-in User

The only user-based metadata card rules you can use are ones where you fill a property with the logged-in user information. In other words you can fill a property such as "Document Owner" with the current user with a SetValue rule, but you cannot use the current user in the rule filters. The filters are based on the object metadata only.

You can read more about the available configuration options in Configuring the M-Files Metadata Card.

Hi Joonas,

I went through the official M-Files documentation that you linked (and that I had reviewed before posting this discussion), but I found it to be quite superficial and it didn’t provide a solution for my specific case.

Moreover, i had already tried using the "Document Owner" property with a SetValue rule to automatically fill it with the current logged-in user (see attached screenshot from my M-Files Admin).

However, this approach didn’t work because "Document Owner" refers to a specific user who needs to be assigned manually to that single document. While this is possible, it involves a lot of manual work and doesn't fully address the goal.

However, the issue is there's no property or filter in the metadata card configuration that dynamically references the currently logged-in user. This limitation makes it difficult to adjust metadata fields based on who is logged in.

The goal here is to keep the metadata card simple and clean for certain end users — for example, a certain highly positioned employee who doesn't need to see every single metadata field. The idea is to display only the relevant fields for certain users while hiding more technical or detailed metadata. 

• For a senior executive of a company, the metadata card should only show minimal metadata for certain document classes like "purchase invoice" or "purchase credit memos", to keep things as simple as possible.

Is there perhaps any other method or a workaround to achieve this without resorting to manual assignments?
Maybe by using a Vault Application or a VBScript to control how the metadata card looks for a specific logged-in user? 

Thanks again for your help!

Hi Joonas,

I went through the official M-Files documentation that you linked (and that I had reviewed before posting this discussion), but I found it to be quite superficial and it didn’t provide a solution for my specific case.

Moreover, i had already tried using the "Document Owner" property with a SetValue rule to automatically fill it with the current logged-in user (see attached screenshot from my M-Files Admin).

However, this approach didn’t work because "Document Owner" refers to a specific user who needs to be assigned manually to that single document. While this is possible, it involves a lot of manual work and doesn't fully address the goal.

However, the issue is there's no property or filter in the metadata card configuration that dynamically references the currently logged-in user. This limitation makes it difficult to adjust metadata fields based on who is logged in.

The goal here is to keep the metadata card simple and clean for certain end users — for example, a certain highly positioned employee who doesn't need to see every single metadata field. The idea is to display only the relevant fields for certain users while hiding more technical or detailed metadata. 

• For a senior executive of a company, the metadata card should only show minimal metadata for certain document classes like "purchase invoice" or "purchase credit memos", to keep things as simple as possible.

Is there perhaps any other method or a workaround to achieve this without resorting to manual assignments?
Maybe by using a Vault Application or a VBScript to control how the metadata card looks for a specific logged-in user? 

Thanks again for your help!

It's not currently possible to modify the metadata card behavior based on the logged-in user except for filling a property default value (SetValue rule). 

My suggestion would be to keep the more technical and detailed properties in property groups which are collapsed by default for all users. Then those users who need to see additional information can expand those groups.