You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e6f6a0f
Browse filesBrowse the repository at this point in the historyBrowse files
improvement(config): derive enterprise flags from one registry, add REGISTRATION_MODE, merge vLLM and LiteLLM (#10271)
* improvement(config): derive enterprise flags from one registry and merge the vLLM and LiteLLM providers
* improvement(auth): replace the three signup toggles with REGISTRATION_MODE
* fix(config): address review findings
* fix(setup): advise the registration mode in effect; refresh docs fence sizes
* improvement(config): simplify the registry and registration seams; retire the sandbox readiness marker
* fix(config): expose the registration mode through getRegistrationMode
* chore(docs): refresh the compatibility baseline after rebasing
* fix(providers): use static log messages in the self-hosted core; document registration helpers
Copy file name to clipboardExpand all lines: apps/docs/content/docs/chat/mailer.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ Sim Mailer gives an enabled workspace an email address. Send or forward a messag
11
11
12
12
A workspace **Admin** configures the inbox. On Sim Cloud, availability follows the workspace's Max or Enterprise plan and active billing, rather than the sender's individual plan.
13
13
14
-
On self-hosted deployments, availability depends on configured Chat and email services. `INBOX_ENABLED` or billing-disabled configuration can allow access, but the required Chat service key must still be configured. See [self-hosted environment variables](/platform/self-hosting/environment-variables).
14
+
On self-hosted deployments without billing, the inbox is on by default. Set `INBOX_ENABLED=false` to turn it off; that closes it on the server and removes it from the interface. It still needs the Chat service key and email services configured to work. See [self-hosted environment variables](/platform/self-hosting/environment-variables).
15
15
16
16
Members keep their own workspace permissions when submitting email tasks. An allowed external email sender can submit read-only tasks; allowlisting does not grant workspace membership, workflow execution, mutation access, or raw-secret access.
Copy file name to clipboardExpand all lines: apps/docs/content/docs/platform/enterprise/access-control.mdx
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -147,7 +147,6 @@ On billing-disabled deployments, enable permission groups through the enterprise
147
147
148
148
```bash
149
149
ACCESS_CONTROL_ENABLED=true
150
-
NEXT_PUBLIC_ACCESS_CONTROL_ENABLED=true
151
150
```
152
151
153
152
The enterprise master configuration can enable the feature; an explicit feature value takes precedence. Billing-enabled self-hosted deployments still require Enterprise. See [self-hosted enterprise setup](/platform/enterprise/self-hosted).
Copy file name to clipboardExpand all lines: apps/docs/content/docs/platform/enterprise/audit-logs.mdx
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -118,7 +118,6 @@ On billing-disabled deployments, enable audit logs through enterprise configurat
118
118
119
119
```bash
120
120
AUDIT_LOGS_ENABLED=true
121
-
NEXT_PUBLIC_AUDIT_LOGS_ENABLED=true
122
121
```
123
122
124
123
Explicit feature values take precedence over the enterprise master setting. Billing-enabled self-hosted deployments retain the Enterprise gate. See [self-hosted enterprise setup](/platform/enterprise/self-hosted).
Copy file name to clipboardExpand all lines: apps/docs/content/docs/platform/enterprise/custom-blocks.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ import { Callout } from '@/components/ui/callout'
7
7
8
8
Publish a workflow as a custom block so teammates can provide its inputs and use selected outputs without access to its source workflow. The block always runs the source's latest deployment. Use it for a shared knowledge lookup, an authenticated internal API, an enrichment step, or a prompt and guardrail maintained in one place.
9
9
10
-
Publishing and managing a block requires admin access to its source workspace. Billing-enabled deployments require an Enterprise organization. On billing-disabled deployments, enable the custom-block feature through enterprise configuration or `CUSTOM_BLOCKS_ENABLED=true` and `NEXT_PUBLIC_CUSTOM_BLOCKS_ENABLED=true`. An organization is still required; see [self-hosted enterprise setup](/platform/enterprise/self-hosted).
10
+
Publishing and managing a block requires admin access to its source workspace. Billing-enabled deployments require an Enterprise organization. On billing-disabled deployments, enable the custom-block feature through enterprise configuration or `CUSTOM_BLOCKS_ENABLED=true`. An organization is still required; see [self-hosted enterprise setup](/platform/enterprise/self-hosted).
Copy file name to clipboardExpand all lines: apps/docs/content/docs/platform/enterprise/data-drains.mdx
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -248,10 +248,9 @@ Enable the feature through enterprise configuration or explicitly set:
248
248
249
249
```bash
250
250
DATA_DRAINS_ENABLED=true
251
-
NEXT_PUBLIC_DATA_DRAINS_ENABLED=true
252
251
```
253
252
254
-
An explicit feature value takes precedence over `ENTERPRISE_ENABLED`. When disabled, the page is hidden, mutating drain requests return `404`, and the dispatcher does no work. Billing-enabled deployments retain the Enterprise gate. Keep server and public feature configuration aligned; `bunx sim-setup doctor` checks the pair. See [self-hosted enterprise setup](/platform/enterprise/self-hosted).
253
+
An explicit feature value takes precedence over `ENTERPRISE_ENABLED`. When disabled, the page is hidden, mutating drain requests return `404`, and the dispatcher does no work. Billing-enabled deployments retain the Enterprise gate. See [self-hosted enterprise setup](/platform/enterprise/self-hosted).
255
254
256
255
The dispatcher requires scheduled calls to `GET /api/cron/run-data-drains`. Set the same `CRON_SECRET` on the app and its caller; the endpoint returns `401` when it is unset. Generate a secret if needed, then install it in both configurations:
Copy file name to clipboardExpand all lines: apps/docs/content/docs/platform/enterprise/data-retention.mdx
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -128,7 +128,6 @@ On billing-disabled deployments, enable retention through enterprise configurati
128
128
129
129
```bash
130
130
DATA_RETENTION_ENABLED=true
131
-
NEXT_PUBLIC_DATA_RETENTION_ENABLED=true
132
131
```
133
132
134
133
An explicit feature value takes precedence over the enterprise master configuration. No plan-based default window is introduced: configure the windows you intend to apply.
Copy file name to clipboardExpand all lines: apps/docs/content/docs/platform/enterprise/forks.mdx
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -188,7 +188,6 @@ On billing-disabled deployments, enable forking through enterprise configuration
188
188
189
189
```bash
190
190
FORKING_ENABLED=true
191
-
NEXT_PUBLIC_FORKING_ENABLED=true
192
191
```
193
192
194
193
Explicit feature values take precedence over the master configuration. Billing-enabled self-hosted deployments still require Enterprise. See [self-hosted enterprise setup](/platform/enterprise/self-hosted).
Copy file name to clipboardExpand all lines: apps/docs/content/docs/platform/enterprise/index.mdx
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,6 @@ On a self-hosted deployment with billing disabled, enable enterprise features th
26
26
27
27
```bash
28
28
ENTERPRISE_ENABLED=true
29
-
NEXT_PUBLIC_ENTERPRISE_ENABLED=true
30
29
```
31
30
32
31
Individual feature flags override the master switch. Most enterprise settings also need an organization that owns the workspace. Choose one instance-wide organization or provision separate organizations through the Admin API.
Copy file name to clipboardExpand all lines: apps/docs/content/docs/platform/enterprise/scim/index.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ Configure [SSO](/platform/enterprise/sso) separately for authentication. SCIM ca
16
16
17
17
- On Sim Cloud, use an Enterprise organization and an organization owner or admin account.
18
18
-[Verify every email domain](/platform/enterprise/verified-domains) you will provision. Sim refuses account creation or an email change to an unverified domain.
19
-
- On self-hosted deployments, enable SSO to reach **Single sign-on → Provisioning**, and enable SCIM. The enterprise master pair enables both; individual setup uses `SSO_ENABLED`, `NEXT_PUBLIC_SSO_ENABLED`, `SCIM_ENABLED`, and `NEXT_PUBLIC_SCIM_ENABLED`. See [Self-hosted SSO setup](/platform/enterprise/sso#self-hosted-setup) and [Deployment and upgrades](#deployment-and-upgrades).
19
+
- On self-hosted deployments, enable SSO to reach **Single sign-on → Provisioning**, and enable SCIM. `ENTERPRISE_ENABLED`enables both; individual setup uses `SSO_ENABLED`and `SCIM_ENABLED`. See [Self-hosted SSO setup](/platform/enterprise/sso#self-hosted-setup) and [Deployment and upgrades](#deployment-and-upgrades).
20
20
21
21
## Plan membership and access
22
22
@@ -205,7 +205,7 @@ While the connection is disabled, **Lock managed membership** and **Disable just
205
205
Apply database migrations before the new application code. The SCIM tables and suspension fields are additive, allowing older code to run against the expanded schema during rollout.
206
206
207
207
<Callouttype="warn">
208
-
Keep `SCIM_ENABLED=false`and `NEXT_PUBLIC_SCIM_ENABLED=false`until all older application instances and workers are drained. Older code does not enforce SCIM suspension or explicit permission-group membership. These explicit flags also override the hosted default.
208
+
Keep `SCIM_ENABLED=false` until all older application instances and workers are drained. Older code does not enforce SCIM suspension or explicit permission-group membership. This explicit flag also overrides the hosted default.
209
209
</Callout>
210
210
211
211
After SCIM has suspended accounts or established managed access, rolling back to code that predates SCIM is unsafe: it cannot enforce those restrictions. Disabling synchronization does not undo suspension or restore earlier membership semantics.
0 commit comments