This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Help Permission Problem!

Former Member
Former Member
HI, Hope someone can help. We want users to be able to see what is populated in the status field but not change it. When we set the permission to see it but not edit. The word shows as hidden instead of what the status actually is. So for example if we set this status field to employed by another user. I want this user to see its set as employed but I don't want them to be able to edit.

Thanks
Emma

  • Hi Emma
    You need to look at the permissions for your Status Property as well as permissions for the Value List referred to by that property and perhaps even at permissions for the individual values in that list. Users need at least Read permissions for all of those items as well as for the object itself. You could give Read permissions to All Internal Users and Edit permissions to a Named Access Control List - eg. HR Department, if that covers your needs. You can also change permissions to the object or to individual properties as part of the actions in your workflow. Some people may need Edit permissions early in the flow and only Read permissions later on.
    I have attached an image that illustrates permissions for a property. It has Read permissions for All internal and external users - you should probably NOT allow external users to view your property!
    BR, Karl
  • Former Member
    Former Member
    Hi guys, need help in setting up permissions.

    I have an object 'Client'. Our company is composed of business units, each of them has its own clients. Is it possible to set permissions automatically to restrict the clients to be private in each business units so each business units can only see their own database.

    As of now, the only thing I am able to do is I created each business units a NACL, and manually select the group everytime an object is created. This is not good enough because each business units might forgot to select their own NACL. The same goes for other objects.

    Thanks,
    David
  • Hi David
    I assume you have business units as an object type and that for every business unit you have one or more multiselect properties holding the employees working in that unit.
    I also assume that in your client class you have a property that ties the client to one or more business units.
    With that in place you can use automatic permissions and restrict access to client objects to those employees who are listed in the relevant business unit. And you can let those restrictions apply to documents related to the client as well.
    BR, Karl
  • Former Member
    Former Member
    Currently I have Business Unit Property as Value list. Do you mean I need to convert this property to object type to meet my requirement? Thanks

    BR, David
  • Yes. It is a simple process - you can convert the value list to an object type. That will not have side affects. When that is done you should add at least one property to the new class so that you can select the employees who are working in each business unit. You may want to have Business Unit Managers in one property and other employees in a different property to give yourself the opportunity to set different permissions. Then you can start using automatic permissions.
    Please create a sandbox environment and test these procedures before you implement them in your working environment.
    Karl
  • Former Member
    Former Member
    Hi Karl, thanks for your answer. Actually I already created some of the structure. But my problem is the document classes. If I create now a document, it is still showing with other business units. The only thing that is hidden is the property Business Unit, etc.

    BR,
    David
  • You need to activate Automatic Permissions on your Business Unit class. Restrict permissions of objects that refer to this class, then use the properties specifying the employees, and specify which permissions each type of employees should have. You probably want to remove All internal users from the permissions. If your properties select employees directly from M-Files users, then you can use the properties directly. If you are selecting from a list of Employees which in turn has a property M-Files User, then use indirect reference like I have on the Project Manager.M-Files user in the screenshot. The screenshot is from a setup for projects but is can be used the same way for your business units.
    With that in place any document and any client referring directly to your business unit should have restricted access.
    In the document classes you should be able to have the Business Unit property filled with an automatic value based on the client, it refers to.