> For the complete documentation index, see [llms.txt](https://docs.simptel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.simptel.com/tf-platform/administration/organizations/projects/tenants/cors.md).

# CORS

This article describes an overview of Cross-Origin Resource Sharing within the platform

### What is CORS? <a href="#seo-faq-pairs-what-is-cross-origin-resource-sharing" id="seo-faq-pairs-what-is-cross-origin-resource-sharing"></a>

Cross-Origin Resource Sharing (CORS) is a mechanism that allows web applications to make requests to resources hosted on different domains.&#x20;

The platform lets you configure CORS at the tenant level, enabling precise control over cross-origin access for improved security and flexibility.

### Best Practices

* Regularly review and update your CORS settings to align with security requirements.
* Always use HTTPS in production for secure communication.
* Avoid using the wildcard `*` in production; explicitly specify allowed origins.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.simptel.com/tf-platform/administration/organizations/projects/tenants/cors.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.