Access
Deployment endpoints, CORS allowed origins and (managed plans) regions.
Last updated
Deployment endpoints, CORS allowed origins and (managed plans) regions.
Where: Project → Settings → Access · /projects/<project>/settings?tab=Access
Control how your project is reached: the addresses SDKs and services should call, and the browser origins that may call them. On managed and Enterprise plans the data Region settings also live here; self-hosted installs have no regions.
Screenshot TODO — capture comes from testing-plan area 17-project-settings.
Read-only addresses discovered from the Hub /echo endpoint — use them when configuring SDKs or external services. Each URL opens in a new tab and has a copy button.
API URL / API version
Base address and version of the data API — on managed plans, for the project's primary region.
Hub URL / Hub version
Base address and version of the management (Hub) API.
Admin portal URL
The canonical portal address. If Brand → Admin portal URL sets an override, the effective URL is shown underneath.
The websites that may call the project's API from the browser. Edit opens a modal with a comma-separated list; whitespace around entries is trimmed. Add every domain where your app or admin portal runs:
http://localhost:3000,https://myproject.comA successful save shows "Project settings updated". Requests from origins not on the list are blocked by the browser's CORS check.
Primary region — where the project's main database and control data live. It is fixed once set and shown read-only.
Additional regions — rendered only when the backend marks the project as eligible for multi-region; other projects see an information notice instead. Tick the regions where app-data databases may also be placed and press Save regions. A region that still hosts a database cannot be removed — delete the database first. Constraint errors from the server are shown on the tab.
See Account & Projects → Projects.
Endpoints: update-project-allowed-origins, update-project-regions.
Last updated