Domain Separate Templates?

[kevinfrost471]

Is there a way to separate templates by Domain?       I know I can limit visibility by groups but I was wondering if they could be domain separated.     I have a client domain where my users working and logging into that domain can see other templates that don't relate to that client.       The only thing I can think of now is to create group called Template users in my main domain and add everyone to it.   Then change the group field on the templates I want them all to see to that new group name and uncheck the global checkbox.     Then for my users working in the client domain - create templates there and add a group name that exists in that domain into the field on those templates.

Any help is - as always appreciated.

[Carmelo Pisani]

I've just been advised by Service Now support on the basis of the following documentation

Domain assignment

Any table with a sys prefix cannot be domain separated.

In particular I've been advised that I can't add this attribute to sys_template. I presume this is a flaw in the documentation and there are no technical reasons why we can't do this.

We certainly don't want different customers viewing other customer's templates. After all that is the point of domain separation

[Denise Smith]

Is there any links or more relevant/new information on this topic? Much of this is years ago.

I have domain separated instance and if user picks domain in picker, I wish them only to be able to 'create' templates for that domain. If they have multiple domains.. we wish to lock the template down to the domain they chose. 

But we also wish to have proposal/templates approved by groups within their domain too.

Today, not a lot of domain information and standard changes that I see.