---
component: ROOT
version: "2026.1"
slug: ROOT/administration/anonymous-access
canonical_url: "https://docs.grdev.net/develocity/2026.1/administration/access-control/anonymous-access/"
title: "Anonymous Access"
description: "Configure permissions for unauthenticated users in Develocity."
keywords:
  - "authentication"
  - "access control"
  - "admin"
status: current
---

<!-- llms-index: https://docs.grdev.net/develocity/llms.txt -->

# Anonymous Access

<a id="preamble"></a>

Configure the level of access granted to users who aren’t logged into Develocity.

Anonymous access allows developers to publish builds without per-user authentication, simplifying setup. Evaluate it carefully against your security and data privacy requirements.

<a id="understanding-anonymous-access"></a>

## Understanding Anonymous Access

By default, Develocity allows anonymous users to **view** and **create** Build Scan data. This allows developers to publish and analyze builds without authenticating.

> [!IMPORTANT]
> Anonymous access to the built-in Build Cache node is disabled by default. Users must authenticate to interact with the cache unless explicitly modified in the service settings.

<a id="configure-via-the-user-interface"></a>

## Configure via the User Interface

To modify anonymous permissions in the Develocity UI:

1.  Log in to Develocity as a user with the **Administrator** role.
    
2.  Navigate to **Administration**  **Access control**  **Anonymous access**.
    
3.  Select the desired access level or specific permissions for unauthenticated users.
    
4.  Click **Save** to store the settings.
    
5.  Click **Apply and restart** in the upper-right corner to activate them.
    

> [!IMPORTANT]
> Applying configuration may take several minutes.

![Anonymous Access Configuration in Develocity UI](https://docs.grdev.net/develocity/2026.1/administration/access-control/anonymous-access/../../_images/dv-ui-access-control-anonymous-access.png)

Anonymous Access Configuration in Develocity UI

<a id="configure-via-unattended-configuration"></a>

## Configure via Unattended Configuration

If you are managing Develocity using a GitOps or automated workflow, you can define the global settings using [Unattended Configuration](https://docs.grdev.net/develocity/2026.1/administration/unattended-configuration/). Depending on your deployment strategy, you can provide these settings either as Integrated configuration within your _values.yaml_ or as a **Standalone** configuration file.

```yaml
version: 15
systemPassword: "«hashed-system-password»"
auth:
  anonymousPermissions:
    - viewScan
    - publishScan
  external: null
  projects:
    acceptAnonymousProjects: true
    enabled: false
```

<a id="deployment-templates"></a>

### Deployment Templates

Download the appropriate YAML template to begin your infrastructure configuration.

_For Develocity versions 2025.3 and prior, see the [2025.2 Administration Guide](https://docs.grdev.net/develocity/legacy/helm-admin/2025.2) or the [2025.3 Administration Manual](https://docs.grdev.net/develocity/2025.3/administration/admin-manual/)._

<table><tbody><tr><td class="hdlist1"><strong>Cluster Deployment</strong></td><td class="hdlist2">Example template for cluster orchestration. gradle-enterprise-config-schema-15.yaml SHA256 ASC ASC SHA256</td></tr><tr><td class="hdlist1"><strong>Standalone Deployment</strong></td><td class="hdlist2">Example template for standalone setup. gradle-standalone-config-schema-15.yaml | SHA256 | ASC | ASC SHA256</td></tr></tbody></table>

> [!IMPORTANT]
> Pre-deployment Checklist Backup: Export your current settings via Administration  Import/export before applying changes. Deployment: After updating your values.yaml, re-deploy using Helm. Impact: This triggers service restarts and may take several minutes to complete. See Unattended Configuration for details.

<a id="security-considerations"></a>

## Security Considerations

*   **Data Exposure:** Enabling `VIEW_BUILD_SCANS` anonymously means anyone with network access to Develocity can see project names, dependency versions, and environment variables included in scans.