> ## Documentation Index
> Fetch the complete documentation index at: https://docs.replit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Source control settings

> Require Git remotes and private repositories for apps in your organization.

Use source control settings to require Git-backed publishing and control whether team members can use public repositories.

## Source control settings

Open **Settings → Advanced**, then find **Source control settings**. These controls apply publishing and repository requirements across your organization.

### Require Git remote

When enabled, all apps must have local changes pushed to a Git remote before publishing. This ensures that all code changes are tracked in your organization's version control system.

**When to use this setting:**

* All code must be backed up in Git
* You need an audit trail of all code changes
* Your workflow requires code review before publishing

<Note>
  This setting does not apply to apps that were published before the setting was enabled.
</Note>

### Private remotes

Control whether team members can use public Git repositories. When set to require private remotes, team members can only push to private repositories on platforms like GitHub.

Available options:

| Setting | Description |
| - | - |
| **Off** | Team members can use public or private repositories |
| **Require for non-admins** | Non-admin team members must use private repositories |
| **Require for all** | All team members, including admins, must use private repositories |

**When to use this setting:**

* Public code repositories are prohibited
* You need to ensure proprietary code is not accidentally pushed to public repos
* Compliance requirements mandate private version control

## Best practices

* Match Git remote and repository visibility requirements to your organization's source control and review process.
* Review [Privacy and deployment settings](/teams/privacy-and-deployment-settings) before choosing publishing, preview, and export controls.
* Use the guidance in [Security](/teams/security) when configuring scans and vulnerability policies.

## Accessing privacy settings

For the current settings location and publishing controls, see [Privacy and deployment settings](/teams/privacy-and-deployment-settings).

## Privacy settings

For publishing access, development previews, exports, uploads, and deployment geography, see [Privacy and deployment settings](/teams/privacy-and-deployment-settings).

### Private deployments

See [Private deployments](/teams/privacy-and-deployment-settings#private-deployments) for publishing policy options and their scope.

### Password-protected deployments

See [Password-protected deployments](/teams/privacy-and-deployment-settings#password-protected-deployments) for access options and behavior.

### Require private development URLs

See [Protect development previews](/teams/privacy-and-deployment-settings#protect-development-previews) for authentication requirements and caveats.

### Ban source code export

See [Restrict exports and uploads](/teams/privacy-and-deployment-settings#restrict-exports-and-uploads) for the ZIP export control and its limitations.

## Security settings

For vulnerability monitoring and organization-wide scan policies, see [Security](/teams/security).

### Require security scan

See [Require security scans before publishing](/teams/security#require-security-scans-before-publishing) for scan requirements and publishing behavior.

## Related resources

* [Privacy and deployment settings](/teams/privacy-and-deployment-settings) - Configure publishing privacy, previews, exports, and deployment geography
* [Security](/teams/security) - Monitor vulnerabilities and configure scan policies
* [Information Security](/teams/information-security/overview) - Learn about Replit's security practices and compliance standards
* [SAML authentication](/teams/identity-and-access-management/saml) - Configure single sign-on for your organization
* [Groups and permissions](/teams/identity-and-access-management/groups-and-permissions) - Manage team member access with roles and groups