Enterprise Privacy Settings

As an enterprise admin, you can configure organization-wide settings that control how team members interact with code, deployments, and external platforms. These settings help maintain security standards, protect intellectual property, and ensure compliance with enterprise policies.

​

Accessing privacy settings

How to access Privacy Settings

1. Navigate to your enterprise workspace
2. Select Settings
3. Select Advanced to view all available settings

​

Privacy settings

Privacy settings control how apps are published and accessed within your organization.

​

Private deployments

When enabled, all new apps must be published as private. Private apps are only accessible to authenticated members of your organization. When to use this setting: When to use this setting:

• The organization handles sensitive data or proprietary applications
• You need to ensure apps are not accidentally made public
• Compliance requirements mandate restricted access to published applications
• You need to ensure apps are not accidentally made public
• Compliance requirements mandate restricted access to published applications

​

Password-protected deployments

Control whether team members can create password-protected deployments. When enabled, builders can add an additional layer of security by requiring a password to access their published apps. When to use this setting:

• You want to allow sharing apps with external stakeholders without making them fully public
• Teams need to demo applications to clients before wider release
• You require granular access control beyond organization membership

​

Require private development URLs

When enabled, all app development URLs require authentication. If your organization has enabled SAML, development URLs require SSO authentication. When to use this setting: When to use this setting:

• You need to prevent unauthorized access to in-progress applications
• Security policies require all development environments to be protected
• You want to ensure only authenticated team members can view development previews
• Your security policy requires all development environments to be protected
• You want to ensure only authenticated team members can view development previews

​

Ban public apps

When enabled, all new apps are automatically set to private within your organization. Public apps can be forked and have their source code viewed by anyone on the internet. When to use this setting: When to use this setting:

• Organizational intellectual property must remain confidential
• You need to prevent accidental exposure of proprietary code
• Compliance requirements prohibit public code repositories
• You need to prevent accidental exposure of proprietary code
• Compliance requirements prohibit public code repositories

​

Ban source code export

When enabled, team members cannot export app source code as a zip file. This prevents code from being downloaded and shared outside of the Replit platform. When to use this setting: When to use this setting:

• You need to maintain strict control over where source code resides
• Security policies prohibit local copies of code
• You want to ensure all development happens within managed environments
• Your security policy prohibits local copies of code
• You want to ensure all development happens within your managed environment

​

Security settings

Security settings help you enforce vulnerability scanning and other protective measures.

​

Require security scan

Configure whether all apps must pass a security scan before publishing. Security scans detect vulnerabilities, exposed secrets, and other security issues in your code. Available options: When to use this setting: When to use this setting:

• Security compliance requirements must be met
• You want to prevent accidental exposure of API keys or secrets
• You need to ensure consistent security standards across all published apps
• You want to prevent accidental exposure of API keys or secrets
• You need to ensure consistent security standards across all published apps

​

Source control settings

Source control settings help you enforce version control practices and protect your organization’s code repositories.

​

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: When to use this setting:

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

​

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: When to use this setting: 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
• You need to ensure proprietary code is not accidentally pushed to public repos
• Compliance requirements mandate private version control

​

Best practices

​

Related resources

• Information Security - Learn about Replit’s security practices and compliance standards
• SAML authentication - Configure single sign-on for your organization
• Groups and permissions - Manage team member access with roles and groups