Domain Separation - Group override

[petersontamarin]

In my company we have a domain map with internal and external customers, and a MSP teams responsible to provide services to several internal departments and external customers. The Teams in MSP domain provide services to a subset of the customers, so we have visibility Groups for them. Btw this is Jakarta version.

Our problem is: we have Assignments Groups created on TOP, but not all customers should view them to assign Incidents and Changes. In the example below, Assignment Group A should not be viewed in DeptB and CustomerA. But the sys_user_group table does not have sys_override field. So I cannot remove or inactivate it in the child domains as I can do with SLAs for instance.

I was thinking to create a table for Group vs Domain relationship (1:N), add it as Related List in Groups form, and modify the Reference condition for all Assignment Group fields to list only the Groups associated to the record context domain. But maybe there is a better way to resolve this.

What do you recommend?

Thanks

[lalit007]

Hi,

you can simply add Visibility Related list in your Group form (Assignment Group A ) and can add the Domains in which this group should be accessible.

Mark the answer correct, if it helps you.

Regards,

Lalit Bhatt

[petersontamarin]

Hi,

Thanks for your answer, but it does not work. Visibility Group has another objective as far as I understood. It grants the permission to the members of the group to access data from another domain (when they're not child). I am testing here and what I have until now:

If I create a Group on TOP, the users from children domains do not have access to it. Because Group is not considered a process (like SLA). This is data. So Groups need to be global or created in child domain. Based on this how can I achieve this requirement explained in the first post?

[lalit007]

Found something Interesting, it might help in your case...

Managed domain field in Group form

The Managed domain field allows a domain to be manually set rather than allowing the

domain to be assigned based on the Company field. This is typically used to associate a support

group with the appropriate company, but places the group in global so users from all domains

may assign tasks to the group.

[lalit007]

Hi Pete,

i think this is the final answer for this particular question:-

You Can Use ACL's (Record read, write and Delete Access ) to achieve it, since ACL's are global   and not domain separated.

Regards,

Lalit Bhatt