{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":14791,"path":"field-service-management/field-service-scheduling/domain-separation-appt-booking.md","title":"Domain Separation and Appointment Booking","bundle":null,"doc_type":null,"release":"australia","body":"\n# Domain Separation and Appointment Booking\n\nDomain separation is supported for Appointment Booking. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.\n\n## Support level: Basic\n\n\n\n-   Business logic: Ensure that data goes into the proper domain for the application’s service provider use cases.\n-   The application supports domain separation at run time. The domain separation includes separation from the user interface, cache keys, reporting, rollups, and aggregations.\n-   The owner of the instance must set up the application to function across multiple tenants.\n\nSample use case: When a service provider \\(SP\\) uses chat to respond to a tenant-customer’s message, the customer must be able to see the SP's response.\n\nFor more information on support levels, see [Application support for domain separation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/domain-separated-apps.md).\n\n## Domain separation and Appointment Booking overview\n\nDomain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.\n\n## How domain separation works in Appointment Booking\n\nDomain separation adds the following fields and attributes to Appointment Configuration tables:\n\n<table id=\"tableID-appointment_configuration_tables_with_domain_separation\"><thead><tr><th>\n\nTable\n\n</th><th>\n\nFields and Attributes\n\n</th></tr></thead><tbody><tr><td>\n\nAppointment Booking Configuration\\[sn\\_apptmnt\\_booking\\_config\\]\n\n</td><td>\n\nFields-   Domain ID\n-   Domain Path\n\n</td></tr><tr><td>\n\nAppointment Booking Service Configuration\\[sn\\_apptmnt\\_booking\\_service\\_config\\]\n\n</td><td>\n\nFields-   Domain ID\n-   Domain Path\n\n</td></tr><tr><td>\n\nService Configuration Rule\\[sn\\_appmnt\\_booking\\_config\\_rule\\]\n\n</td><td>\n\nAttributes:\n\n domain\\_master=sn\\_apptmnt\\_bookig\\_service\\_config\n\n</td></tr><tr><td>\n\nAdvanced Configurations\\[sn\\_appmnt\\_booking\\_day\\_configuration\\]\n\n</td><td>\n\nAttributes\n\n domain\\_master=sn\\_apptmnt\\_bookig\\_service\\_config\n\n</td></tr><tr><td>\n\nAppointment Booking Lock\\[sn\\_appmnt\\_booking\\_lock\\]\n\n</td><td>\n\nFields-   Domain ID\n-   Domain Path\n\n</td></tr><tr><td>\n\nAppointment Recommendation\\[sn\\_apptmnt\\_recommendation\\]\n\n</td><td>\n\nFields-   Domain ID\n-   Domain Path\n\n</td></tr></tbody>\n</table>**Related topics**  \n\n\n[Domain separation for service providers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/domain-sep-landing-page.md)\n\n"}}