ITSM scenarios

[SravaniPeri]

If there are client A and client B, Client A should not see applications for client B and vice versa how you will do this other than domain separation?

[Sandeep Rajput]

@SravaniPeri If you do not wish to implement domain separation then I recommend having a column on the application table, this column can be called Owner and it should be a reference field referring to a table where your client records are stored.  ACLs can be created on the basis of the owner field and access to the application can be restricted through it.

[rBh]

Hye did u find the answer for it? i am also looking for the same answer

[yashkamde]

Hello @SravaniPeri, @rBh ,

don't know if I'm getting the requirement wrong but can't we do this direct from edit application menu !!

[glideFather]

ahoy @yashkamde,

be careful please, that is only to see that module, but not an actual access (!!!).

Imagine a Module called "Incidents" linking to [incident] table, if you add an admin role, only admin will see this module in the navigator but if someone shares a link with them or they will navigate with the /incident_list.do in the URL (eventually using SN utils) it will not restrict the access.

It must be applied via ACL