Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Domain separation and remote tables

Log in to subscribe to topics and get notified when content changes.

Domain separation and remote tables

This is an overview of domain separation and remote tables. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can then control several aspects of this separation, including which users can see and access data.


Support: Data only

Domain separation provides complete data isolation for domain-specific users. Domain separation in this application is supported at the Data only level, meaning it supports the data security model of separating visibility of data from one domain to another. To learn more, see Application support for domain separation.

How domain separation works with remote tables

When you create standard internal tables, you can add a sys_domain field, which results in domain separation of the data that is stored in the table. This functionality is not supported when you natively create remote tables, which results in lack of domain separation for rows that are added to a remote table.

However, script definitions that you create and associate with a remote table can be domain (data) separated. When you create the script, you can include DomainSupport APIs that provide domain separation support. If the script definition is domain separated, only users that belong to the designated domain can view the data in the remote table.