Problem Portal User Roles and ACL

[murugappan]

Espocrm Version 5.9.4

Hi,

I am facing portal user access level problems. I have created a portal, portal user and portal roles. The user is allowed to access the records under his "account" do read and should be allowed to edit 3 fields (those highlighted in screencap 1). The access have been set to read and edit only (see screecap 1). Setting this alone did not work as this allowed "inline edit" on all fields. So i set the field level access too (see screencap 2). This did not work. There was no edit button or the field was shown as read only. Therefore the user was unable to edit the 3 fields.

Please help

[Maximus]

Hello,
To make a portal user be able to do actions under the 'account' permission scope there should be achieved 2 things:
1. Ther record should be linked to Account. I've noticed that you have the 'Provider Name' link type field. Is this is the renamed Account entity link type field?
2. Your portal user should be linked to the desired Account (open portal user's profile -> 'Accounts' link-multiple type field).

So in your case, if the 'Provider Name' field is the Account field, all you need to do is select 'AMPANG PUTERI SPECIALIST HOSPITAL' in the Accounts field in the portal user's profile.
Does that make sense?

[murugappan]

Maximus thank you for the reply. The user is linked to an account. The account field exists in the record, it is not shown on this layout. The filtering works well. I get the records relating to the user related accounts only. The provider name is not labelled as "account". Refer to screencap 4 where you can see the Corporate Name. This field is linked to Account.

[murugappan]

Maximus Hi, Can i get some urgent help on this please?

[Maximus]

Hi,
sorry for the delayed reply.
I've tried to reproduce your issue, but in my case everything works as it should.
Please try to clear the browser cache with its advanced settings and try again. I am sure this is the cache issue.

[murugappan]

Maximus Thank you so much for the wonderful assistance. I regret i sent you on wild goose chase. After some testing the problem did not resolve and then i decided to test it in my staging instance. It works there. I guess the test instance must have been corrupted.

Thank you once again.