# Notification Center Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Faccount-management%2Ffedramp%2Fnotification-center.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Faccount-management%2Ffedramp%2Fnotification-center.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.) Notification Center in the FedRAMP environment is deliberately narrower than in the commercial regions. Every destination a notification can reach has to be FedRAMP Authorized in its own right, which rules out most of the connectors available elsewhere. This page describes what is available on GOV1 and why. For how Notification Center works generally, see [Notification Center](https://coralogix.com/docs/user-guides/notification-center/introduction.md). ## Available connectors[​](#available-connectors "Direct link to Available connectors") **ServiceNow is the only connector available**, and it targets [Cases](https://coralogix.com/docs/user-guides/cases/overview.md). Every other connector available in the commercial regions is unavailable in the FedRAMP environment, including Slack, Microsoft Teams, PagerDuty, email, and Generic HTTPS. Cases are also the only entity Notification Center routes here. Alerts do not appear as a notification entity, and an alert reaches ServiceNow through the Case it opens. When you configure an alert, the notification step offers Cases alone. How that surfaces depends on how you create connectors: * **In the Coralogix UI**, only the connectors available in this environment are offered. Unsupported connectors are not listed, so there is nothing to select and no error to run into. * **Through Terraform or the API**, a request specifying an unsupported connector type is rejected. The reason is the destination rather than Coralogix: a notification leaves the authorization boundary when it is delivered, so the receiving service has to carry its own FedRAMP authorization. Slack is not FedRAMP Authorized (GovSlack is a separate offering), Generic HTTPS allows arbitrary uncontrolled destinations, and the rest are either unauthorized or not authorized for this use. ### Requesting an additional connector[​](#requesting-an-additional-connector "Direct link to Requesting an additional connector") Before any connector is added to the FedRAMP environment, it has to be verified on the [FedRAMP Marketplace](https://marketplace.fedramp.gov/): * The service must be listed as **FedRAMP Authorized**. **In Process** and **FedRAMP Ready** are not sufficient. * The specific Cloud Service Offering must match the intended use. A vendor holding an authorization for one offering does not extend it to another. To request one, contact your account representative or email . ## ServiceNow must be a GCC instance[​](#servicenow-must-be-a-gcc-instance "Direct link to ServiceNow must be a GCC instance") The ServiceNow instance you connect to must be a Government Community Cloud (GCC) instance, with a URL of the form: ``` https://your-instance.servicenowservices.com ``` A commercial ServiceNow instance (`*.service-now.com`) is rejected. Only ServiceNow's GCC offering holds FedRAMP authorization, so sending Coralogix data to a commercial instance would move it outside the authorization boundary. ### One-directional only[​](#one-directional-only "Direct link to One-directional only") The connector sends records from Coralogix to ServiceNow. Updates made in ServiceNow are not synchronized back to the Coralogix Case. In the commercial regions this synchronization is bidirectional. Plan your workflow so that Coralogix remains the system of record for Case state. ## Presets[​](#presets "Direct link to Presets") **System presets only.** Custom presets cannot be created in the FedRAMP environment, so notifications use the ServiceNow system preset as it ships. That preset sends the same content it sends in the commercial regions. A ServiceNow GCC instance sits inside the FedRAMP authorization boundary, so the notification carries its usual fields rather than a reduced set. ## What this means for setup[​](#what-this-means-for-setup "Direct link to What this means for setup") Otherwise, Notification Center behaves as it does elsewhere. Routers, routing rules, and routing labels work the same way, and Cases still drive notifications through their [ownership tags](https://coralogix.com/docs/user-guides/infrastructure/infrastructure-explorer/ownership.md). The [routing documentation](https://coralogix.com/docs/user-guides/notification-center/routing/introduction.md) therefore applies here as written. Read its examples with this environment in mind: they route alert entities to connectors such as Slack and PagerDuty, none of which are available here, so treat them as illustrations of the matching logic rather than configurations you can copy. The practical differences when you configure it: | | FedRAMP environment | | ------------------- | ------------------------------------------------------------------------- | | Connectors | ServiceNow only, GCC instance | | Creating connectors | The UI offers only supported types. Terraform and the API reject the rest | | Entity type | Cases only, alerts route through their Case | | Presets | System presets only, with the same content as commercial | | ServiceNow sync | Coralogix to ServiceNow only | ## Related resources[​](#related-resources "Direct link to Related resources") [FedRAMP environment](https://coralogix.com/docs/user-guides/account-management/fedramp.md)[ServiceNow destination type](https://coralogix.com/docs/user-guides/notification-center/destination-types/servicenow.md)[Notification Center introduction](https://coralogix.com/docs/user-guides/notification-center/introduction.md)[Cases](https://coralogix.com/docs/user-guides/cases/overview.md) ## Next steps[​](#next-steps "Direct link to Next steps") Review how your tenant reaches the environment in [Access and authentication](https://coralogix.com/docs/user-guides/account-management/fedramp/access.md).