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
Organization owners and admins open **Settings → Security** to manage session policies and view outbound IP addresses. [Single sign-on](/platform/enterprise/sso) remains a separate settings page for identity providers, verified domains, and provisioning.
9
7
10
8
## Session policies
@@ -17,18 +15,10 @@ See [Session policies](/platform/enterprise/session-policies) for limits, defaul
17
15
18
16
## Outbound IP addresses
19
17
20
-
When an outbound gateway has been configured for your organization, this section lists the IPv4 addresses published by your deployment administrator. Use the copy button beside each address to copy it in `/32` format. Allowlist **every listed address** on the destination firewall.
21
-
22
-
This section is read-only. Viewing or copying addresses does not provision a gateway or change routing. Contact Sim support for hosted deployments, or your deployment administrator for self-hosted installations, to arrange routing and confirm which connections it covers.
18
+
Copy your organization's configured addresses in `/32` format and allowlist **every listed address** on the destination firewall. These addresses apply to supported HTTPS connections from Sim and its background workers.
23
19
24
-
If dedicated IPs are not configured, the page says so. If settings cannot be loaded, use **Try again**. A paused-routing message means your administrator has blocked outbound routing.
25
-
26
-
<Callouttype="warn">
27
-
The listed addresses describe configured routing, not a successful connectivity test. Verify each required connection from both Sim and its background jobs before relying on the allowlist. Browser traffic and traffic originating inside external services do not use this gateway. The current mandatory-gateway mode also blocks unsupported transports, including remote sandbox creation and raw database connections; it does not silently send them through another network.
28
-
</Callout>
20
+
Contact Sim support or your deployment administrator to configure dedicated IPs and confirm connection coverage.
29
21
30
22
## Availability
31
23
32
24
On Sim Cloud, Security settings require an Enterprise organization and an owner or admin role. On self-hosted deployments, the outbound IP section is available to organization administrators; session controls appear only when session policies are enabled. See [self-hosted enterprise configuration](/platform/enterprise/self-hosted).
33
-
34
-
Existing links to the former **Session policies** and **Network** pages continue to open Security settings.
Copy file name to clipboardExpand all lines: apps/docs/content/docs/search/gitlab.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
@@ -25,7 +25,7 @@ Use a self-managed GitLab instance reachable by Sim over HTTPS. The administrato
25
25
26
26
The CSV path checks the token's identity and project access. It does not require administrator directory access or a custom admin role.
27
27
28
-
If your GitLab instance restricts inbound traffic by source IP, coordinate the allowlist before connecting. When dedicated routing is configured, organization admins can copy its published addresses from [Settings → Security → Outbound IP addresses](/platform/enterprise/security#outbound-ip-addresses). Confirm access from both the application and background sync jobs; seeing the addresses in Settings does not verify connectivity.
28
+
If your GitLab instance restricts access by source IP, allowlist the configuredaddresses from [Settings → Security → Outbound IP addresses](/platform/enterprise/security#outbound-ip-addresses). Confirm connectivity from Sim and its background sync jobs before the initial sync.
29
29
30
30
<Callouttype="warn">
31
31
CSV files define access in Sim. Each mapped user listed for the selected project can read all of that source's indexed, non-confidential content. Sim does not infer that user's GitLab role or feature restrictions in this path. Include only users who should have that access, and replace the files whenever memberships or email mappings change.
0 commit comments