diff --git a/Kubernetes-Backups-and-Recovery-with-K8up.md b/Kubernetes-Backups-and-Recovery-with-K8up.md
index 332ee29..01f780f 100644
--- a/Kubernetes-Backups-and-Recovery-with-K8up.md
+++ b/Kubernetes-Backups-and-Recovery-with-K8up.md
@@ -165,7 +165,7 @@ PR ref: https://github.com/seaweedfs/seaweedfs/pull/5034
    helm install seaweedfs . -f test-values.yaml --wait
    ```
 
-5. Expose the filer service via a LoadBalancer (servicelb in k3s). This will let us view the admin UI as well as reach the S3 endpoint during the demo.
+5. Expose the filer service via a LoadBalancer (servicelb in k3s). This will let us view the filer's file browser UI as well as reach the S3 endpoint during the demo.
 
     ```bash
     /bin/cat << EOF > service.yaml
diff --git a/S3-Credentials.md b/S3-Credentials.md
index 30c175e..e07be8c 100644
--- a/S3-Credentials.md
+++ b/S3-Credentials.md
@@ -44,7 +44,27 @@ weed s3 -config=/path/to/s3.json -filer=localhost:8888
 
 Store configuration in the filer using the credential manager. This allows dynamic configuration updates without restarting the S3 server.
 
-### 3. Environment Variables (Fallback)
+### 3. Admin UI (Web Interface)
+
+Use the SeaweedFS Admin UI to manage S3 credentials through a web interface:
+
+```bash
+# Start the admin interface (separate from filer)
+weed admin -masters=localhost:9333
+
+# Access the admin UI (default port 23646)
+http://localhost:23646
+```
+
+Navigate to **Object Store → Users** (`/object-store/users`) to:
+- **Create Users**: Add new S3 users with email and permissions
+- **Edit Permissions**: Modify existing user access levels
+- **Manage Access Keys**: Generate and delete access key pairs
+- **View User Details**: Check user activity and current permissions
+
+The Admin UI stores credentials in the filer using the same filer configuration method, so changes are automatically synchronized across all S3 servers connected to the same filer.
+
+### 4. Environment Variables (Fallback)
 
 Use AWS standard environment variables as a fallback when no other configuration is available:
 
@@ -65,10 +85,13 @@ SeaweedFS uses the following priority order for S3 credentials:
 
 1. **Configuration File** (if `-config` option is provided)
 2. **Filer Configuration** (if available and no config file)
-3. **Environment Variables** (fallback only)
+3. **Admin UI** (web interface that stores in filer configuration)
+4. **Environment Variables** (fallback only)
 
 Higher priority methods completely override lower priority methods - there is no merging or supplementing.
 
+**Important**: Admin UI and Filer Configuration both use the same underlying storage (filer), so they have the same effective priority. The Admin UI provides a user-friendly interface for managing what is stored as filer configuration.
+
 ## Configuration Examples
 
 ### Production Setup
@@ -151,6 +174,7 @@ SeaweedFS supports different reloading mechanisms depending on which authenticat
 |---------------------|-------------|---------------|-------------|
 | **Configuration File** (`-config` option) | ❌ No | ✅ SIGHUP | ❌ No |
 | **Filer Configuration** (credential manager) | ✅ Yes | ✅ Yes | ✅ Yes |
+| **Admin UI** (web interface) | ✅ Yes | ✅ Yes | ✅ Yes |
 | **Environment Variables** | ❌ No | ❌ No | ❌ No |
 
 ### Static Configuration Files
@@ -188,6 +212,17 @@ The server will automatically detect and apply changes:
 I0723 12:35:12.456 auth_credentials_subscribe.go:55] updated /etc/seaweedfs/iam/identity.json
 ```
 
+### Admin UI Configuration
+
+Admin UI changes are automatically applied in real-time since they use the same filer-based storage:
+
+1. **Access Admin UI**: Navigate to `http://localhost:23646`
+2. **Go to Users**: Click **Object Store → Users**
+3. **Make Changes**: Create, edit, or delete users through the web interface
+4. **Automatic Sync**: Changes are immediately applied to all connected S3 servers
+
+The server will show the same automatic detection messages as filer-based configuration since they share the same underlying storage mechanism.
+
 ### Environment Variables
 
 Environment variable changes require a complete restart of the S3 server: