Welcome to OurGrove

Initial Setup Required

Create your first WebUI administrator account. This is separate from your Linux host login.

Find the one-time setup token On a preinstalled OEM machine, first complete the Linux account setup at its screen. On the OurGrove server, sign in with your Linux account and run:

sudo ourgrove-bootstrap-token

The command prints only the token and asks compatible terminals to copy it to your clipboard.

Bootstrap Token

Admin Username One word, 1–32 letters, numbers, dots, underscores, or hyphens.

Admin Email

Admin Password

Use a unique password of at least 8 characters. A longer phrase is better.

Confirm Password

YOUR APPS. YOUR SPACE.

Your Grove.

Checking server…

Checking your server…

Gathering app, backup, and resource information.

CURRENT STATE

At a glance.

Checked with your server

Checking apps, backups, disks, internet, and space…

Your apps

Loading your apps…

Server notifications

The latest server alerts appear here even when email is off.

Loading notifications…

Room to grow.

Server resources

Processor—

Current usage

Memory—

Checking capacity…

Storage—

Checking free space…

Temperature—

Processor temperature

Resource history Charts and refresh settings

Refresh every

CPU Usage

Tracks active CPU time across the host from kernel scheduler counters.

Memory Usage

Shows resident memory pressure using available-vs-total RAM.

Disk Usage

Represents root filesystem occupancy using live statfs values.

CPU Temperature

Die temperature read from on-die thermal sensors via hwmon/thermal subsystem.

Advanced diagnostics API checks, recent probes, and detailed system diagnostics Show details

API Health

Service checks

Recent Health Checks

last 8 checks

Waiting for first probe cycle...

healthy auth-gated degraded offline not yet updated

System Diagnostics

Open Advanced diagnostics to check this server.

LOCAL MODELS FOR YOUR AGENTS

AI.

Choose a local AI engine

Choose what new agents will use. Existing agents keep their connection until you change it. OurGrove recommends an engine using this server's hardware.

StrataAgent focused models and live metrics. Best when OurGrove can match your GPU to a Strata engine. llama.cppFlexible GGUF models on CPU or GPU. A good choice when Strata's GPU requirements are uncertain. NoneHide the AI tab and local AI dashboard. You can restore them from Settings → General at any time.

Checking hardware and installed services…

Strata AI

Checking Strata…

Set up Strata

OurGrove guides setup, keeps model files on this server, and shows when Strata is ready to use.

Want an assistant to help with Strata?

Connect a trusted assistant through MCP to check setup and troubleshoot. Server management access lets it install Strata, change model settings, and recover a failed model choice.

Checking your graphics card…

OurGrove will select a compatible graphics engine when it can identify your card and its runtime.

Graphics hardwareOurGrove checks the available backend before setup.

Graphics engineOurGrove selects an engine when it can identify your card.

Model choice is automatic. Strata chooses a model pack for this hardware on first start; you can change it later.

Change model choice (optional)

Model familyChoose a family to see its model sizes, or leave Automatic for Strata's hardware choice.

Model sizeChoose a family for model sizes. Automatic lets Strata decide.

Context windowLonger conversations use more memory and disk. Contexts above 128K require Custom. Hermes may need at least 64K.

Advanced model options

Parallel requests

Picture input

Conversation memory format

The first start downloads the Strata engine and model files, which can need tens of GB of free disk space. Download and model loading may take a while. OurGrove keeps progress visible if you leave this page.

llama.cpp

Checking local AI…

Connect an AI agent

Choose a downloaded model. OurGrove fills in the private app-network connection for built-in agents. The small 1B starter checks chat connectivity with OpenClaw; Hermes needs a model with at least 64K native context and a 64K served window.

Model for new or installed agents

Turn on llama.cpp and download a model to connect an agent.

Set up llama.cpp

Turn on llama.cpp and download a model. Automatic compute chooses from the hardware OurGrove detects; CPU only is always available.

Run llama.cpp local AI

Store downloaded models on

Checking available storage before model downloads.

Compute options

Use

Context window

Longer windows use more memory. Hermes needs at least 64K and a model that supports it.

Downloaded llama.cpp models

Turn on local AI above, then save and apply to download a model.

Small starter · about 806 MB

Gemma 3 1B. A good first download for testing a local chat connection.

More capable · about 3.4 GB total

Gemma 3 4B can also look at images and follows long conversations (128K context). The download includes its image part; serving 64K context for Hermes also needs more RAM or VRAM.

Download a different GGUF model

Find a GGUF model on Hugging Face. Paste its llama.cpp name, such as owner/repository:Q4_K_M.

Model name

On this server

Turn on local AI to manage models.

Try a downloaded model

Ask a short question to check that a model can answer. This test stays on your server and does not save a conversation.

Model

Your message

Download a model first to try it here.

Connect another app

OpenAI base URL (server LAN IP)

Existing agents configured for llama.cpp can continue using the OpenAI-compatible address http://ourgrove-llama:8080/v1 and a connection key. This internal address does not work from another computer. Keep the key private.

Containers (advanced)

Runtime Containers

				Access	Credentials	Actions
Loading containers...

KEEP WHAT MATTERS

Backups.

Create recovery points, keep nightly copies, and restore with confidence.

[ ... ]

Backup health Checking backup safety...

Looking at local recovery points, schedule, and off-server copies.

Local copy Nightly schedule Off-server copy

SAVED ON THIS SERVER

Recovery points

These archives are stored locally. Download or copy important ones before relying on them for disk-loss recovery.

Saved backups

Restore is always an explicit action and creates a pre-restore safety backup first.

Loading backups...

Recover from another location Find backups on USB, S3 storage, or a NAS

Connect your backup storage in “Schedule and destinations” below, then choose where to look. Backups from your previous server appear here too.

Schedule and destinations Automatic backups and copies off this server

Local recovery points - Checking recovery dates…

Automatic backups Checking... No run recorded

NAS copy Checking... No destination configured Coverage not checked

USB recovery drive Checking... No drive configured Coverage not checked

Object storage copy Checking... No destination configured Coverage not checked

Protection plan

Schedule and destinations

Start with nightly local backups, then choose at least one destination that is physically outside this server.

1. Keep Local Backups

Fast recovery points stored on this server.

Create a backup every night Run at Keep local nightly backups for

days (minimum 3)

Fourteen days is recommended when space allows; three days is the minimum for smaller drives. OurGrove keeps the newest verified recovery point if space runs short. Manual backups remain until you delete them.

Backups you chose to keep Checking manual and pre-restore backups…

Where to keep local backups Checking boot drive and additional storage… Storage location Moving backups copies and verifies existing archives before switching storage.

OurGrove leaves out AI model downloads only when it can verify how to get the exact file again. Other models and prepared Strata files remain in the backup. A full restore needs internet access for downloads that were left out.

2. Copy to a USB Recovery Drive

Keep a removable, verified copy that can be stored away from this server.

USB recovery drive Checking for a configured drive...

Backups contain account recovery keys, credentials, and application secrets. This first USB release supports existing ext4 and exFAT partitions; their contents are not encrypted by OurGrove. Keep the drive physically secure. A later release will be able to prepare an encrypted drive.

Copy backups to this USB drive Copy nightly backups while the drive is connected Keep USB nightly copies for

days (14 recommended; minimum 3)

If the drive is absent, the local backup still succeeds. Connect it before the scheduled time or copy the newest recovery point manually later.

Do not unplug while copying. Wait until OurGrove says “Safe to remove.” A permanently connected USB drive is not a substitute for an off-site copy.

3. Copy to a NAS

Save a copy to a shared folder on another device. Samba and Windows shares use SMB.

NAS connection Checking connected backup storage...

Copy backups to a NAS folder Copy nightly backups to NAS Keep NAS nightly copies for

days (14 recommended; minimum 3)

Manual backups copy to NAS whenever NAS copies are enabled. SMB credentials are stored root-only on this server. NFS access is controlled by the NAS.

Find or connect a NAS share

Find a NAS on this network

Connect a Samba/SMB share on your local network. OurGrove reconnects it after reboot. NFS is also available for devices that use it.

NAS username

NAS password

Select a share first. For Samba/SMB, you can then connect with a username and password or explicitly choose guest access. NFS permissions are managed on the storage device.

Backups hold the passwords and keys for everything on this server and are not encrypted. Use a share with its own login that only you can open, not a guest share everyone on the network can read.

Already know the share?

If scanning finds nothing (some NAS boxes block share listing but still allow a direct connection), enter it directly using the host above.

4. Copy to Object Storage

Use MinIO, Backblaze, Wasabi, Amazon S3, or another S3-compatible place.

Copy backups to S3-compatible storage Keep S3 nightly copies for

days (14 recommended; minimum 3)

Use object storage outside this server for real recovery. Local MinIO is allowed for testing, but it will not protect you if this machine or disk fails.

Changes above do not take effect until they are saved.

How recovery works What is included and how to restore

How recovery works

One complete archive, then copies in safer places

OurGrove builds a rebuild-oriented archive. A local copy is fastest to restore, but only a NAS, object-storage, or downloaded copy protects you when this server's disk fails.

CaptureAccounts, server settings, installed apps and their files, databases and settings.

AutomateRun nightly and keep a predictable number of recent recovery points.

Copy off-serverSend each backup to a NAS or S3-compatible provider, or download it yourself.

Recover deliberatelyChoose a full restore, settings only, or app data only. A safety backup is created first.

Import is safe: selecting “Import backup file” only validates the archive and adds it to Recovery Points. Nothing is overwritten until you explicitly choose Restore.

What a backup does not include

The operating system itself. Recovery starts from a fresh OurGrove install, then puts your settings and apps back.
App programs (Docker images). They are downloaded again from the internet during recovery, so recovery needs a connection.
Large AI model files that have a verified public download. The backup records where to get them and checks them after download; your own or private models stay in the backup.
Files outside OurGrove, such as folders you created on the server by hand, unless an app or file share uses them.

A backup contains passwords and keys for everything on this server. Treat every copy like a house key.

ROOM TO GROW

Disks.

Add internal drives for app files and local backups. Your boot drive is protected.

Checking connected disks…

Space at a glance

See what is writable now

Choose a storage location to see its used and free space. Each location is shown separately so a RAID mirror is not counted twice.

Measuring storage…

Connected drives and boot protection Drive details

Storage pools

Where app files can live

Checking existing pools…

Add ZFS storageChoose internal drives and review the plan

ZFS checks data as it is read. A mirror or RAIDZ pool can repair damaged data from another drive. Snapshots help recover older files, and regular scrubs check stored data for errors.

1. What matters most?

More roomCompare usable space and drive failure protection. Survive a disk failureKeep a pool available if a member fails. Frequent writesGood for busy apps and databases. Local backup spaceKeep a separate copy on this server.

2. Select additional internal drives

Checking available drives…

Select safe internal drives, including unused drives with existing partitions or filesystems. Review their contents before confirming the erase. Boot, USB, and in-use drives stay protected.

3. Compare your options

Select a drive to see plans.

RAID is not a backup. It can help a pool stay available after a disk fails, but it does not undo deletion, corruption, ransomware, or loss of the whole server. Keep another copy on a NAS, offsite service, or removable backup drive.

Where app files live

Choose a pool for larger files

Checking installed apps…

Moving existing app files can take a long time. OurGrove checks the pool again before starting the app.

Which files belong on a pool?

Silo (MinIO)

Put object data on a large pool, and keep a backup elsewhere.

Nextcloud

Put user files on a large pool. Moving an existing installation needs a guided migration.

WeGotWorkSpace

Put content and uploads on a large pool. Its database still needs a backup.

Local backups

Choose the boot drive or a separate pool for a short local history, then keep another copy off this server.

Local backup archives

Choose where recovery points live

Checking local backup destination…

Local backups can use the boot drive or an additional pool. A separate pool helps if the boot drive fails, but either location can be lost with the server to theft, fire, power damage, or a mistaken deletion. Keep a second copy on a NAS, S3, or a safely stored removable backup drive.

MAKE IT WORK FOR YOU

Settings.

Find a setting

Choose a common task below, or use the categories to find all settings.

Local AI

Choose the model engine shown for this server. None hides the AI tab and its dashboard panel for administrators. It does not uninstall an engine or stop an existing model service.

Show local AI

Select Strata or llama.cpp to open its setup. If you add a GPU later, return here to change your choice.

Storage & cleanupSee what apps use, safely clear old downloads, or restore data from removed apps.

Installed app storage

App files, Docker volumes and downloaded images are shown separately so shared image layers are not mistaken for personal data.

Open this section to measure app storage.

Removed does not have to mean lost.

When you uninstall an app and choose Keep data, OurGrove keeps its server-stored accounts, settings and content, if it has any. Reinstall the same app later to bring that data back. Work saved only in your browser or downloaded to your device is separate.

Full backups made while this data is kept include it. Deleting data here removes the server copy; recovery points already created remain separate until they expire under your backup policy or you delete them.

Data from removed apps

Open this section to check for data from removed apps.

Repair saved settingsCheck that OurGrove can read its own saved settings, and start again with empty ones if a file is damaged.

Use this when a settings page says its saved settings could not be read, or an app cannot be installed because of an earlier interrupted install. Nothing is deleted: a file you set aside is kept on the server under a new name.

Open this section to check.

Appearance

Saved automatically in this browser. These settings only affect the management interface, not your installed apps or other devices.

Colour theme

Use light or dark colours, or switch automatically with your device.

Interface animationsAnimate page changes and app cards. Turn off for an interface without movement; status updates still work. Confetti after app installationShow a short confetti animation when an app finishes installing. Success and error messages are always shown.

Time & Region

Timezone

Loading timezone...

Date & Time Format

Loading time format...

Security

My Account

Server Disk Encryption Checking server storage…

Encryption is best configured while installing the server.

TPM automatic unlock is intended to let encrypted servers install nightly updates and restart unattended. OurGrove only reports readiness for now; it will not change disk-encryption keys from the Web UI until recovery and update behavior is fully validated.

Assistant access

MCP keys, app permissions, bot notifications, and access reviews are together under MCP & Assistants.

AI & integrations Assistant connections

Connect an assistant (MCP)

Account-scoped, read-only MCP connection. Admin permissions use a separate key.

Checking bot access…

Allow my bot to connect

MCP endpoint

Client configuration

Choose Streamable HTTP as the MCP transport.
Paste the endpoint above as the server URL.
Add an Authorization header with Bearer, a space, and your access key. Reconnect your assistant after changing keys.

Use HTTPS remotely. The key does not grant dashboard sign-in.

Assistant permissionsApp installation, Strata, and server access

Installation and server management require a separate admin key.

Allow a trusted assistant to install apps

Checking app management…

Installation scope and risks

The admin key can install ordinary catalog apps without another dashboard prompt, downloading third-party software and using storage, memory, CPU, and bandwidth. A faulty or compromised bot could start unintended apps. Apps needing extra host access, a domain, or shared folders still wait for review. Disable access or rotate the key to revoke it.

Allow app installation by MCP

The bot must reconnect with the admin key to receive these tools.

Allow server management

Checking server management…

Server management scope

The admin key can set up Strata, change its model settings, start it, check and install Strata updates, and reconnect configured agents. It can also change Domain & HTTPS settings, run Dynamic DNS updates, and retry certificates. These actions may download large models or interrupt agent requests and public access. Changing this permission rotates the admin key; reconnect the bot. Keys and webhook credentials stay in the dashboard.

Allow server management by MCP

Pending app requests

Review requests from any administrator's assistant here, including when your own MCP key is off. Approving starts that app installation; declining tells the assistant it was not approved.

Checking for app requests…

Access reviewConnected accounts and key review

Accounts with assistant access

Review who has connected an assistant. Keys stay private to each account. Disable your own connection above. For another account, Turn off deletes its assistant keys; that person can create new ones later.

Checking connected accounts…

After checking your connected bots, keys, and pending requests, record the review to restart the reminder clock.

Dashboard two-factor policy

Checking policy…

Require 2FA for

Save policy change

Confirm with your password and a fresh authenticator code or recovery code. Your own 2FA and recovery codes must already be set up.

Your password

Authentication code

User Management

Help with 2FA resets two-step sign-in for someone who lost their phone. It needs 2FA on your own account too; manage yours in Account Settings → Security.

Username	Email	Role	Actions
Loading users...

Username One word; no spaces.

Password

Role

SSH Access

SSH access opens an OS account on this server. Accounts with sudo can administer the whole server. Only add keys you trust.

OS Account	Type	Comment	Fingerprint	Actions
Loading SSH access...

Account

Public Key

Recent Security Events

Sign-in attempts and account changes, with timestamps and source IPs.

Time	Action	Resource	IP
Open this section to load events.

SMB File Sharing

Checking file sharing... Looking for SMB users and app-created shares.

Use a named SMB user for private folders. Guest access is easier for trusted home networks, but anyone who can reach this server on your home network can open, change and delete files in guest shares, without a password.

SMB user	Use	Actions
Loading SMB users...

App Shares

Apps can keep local folders without sharing them on the network. To share or stop sharing an installed app’s folders, open Apps → Your apps → Manage app → Manage shared folders. Turning sharing off keeps the files.

Share	Folder	Access	Connection help
Loading shares...

Server IP Address

Loading network connection…

Address assignment

Address planning

Use an unused LAN address outside the DHCP pool or reserve it in the router. After changing the address, update router forwards and saved connections.

Changes revert after three minutes unless confirmed at the new address.

Phone pairing QR code and connection address

Scan with the OurGrove Android app. If you opened this dashboard over HTTPS, the code signs the phone in as your web account. On HTTP, the app asks for your credentials. Keep the one-use code private; it refreshes while this section is open.

Loading appliance address…

Open larger

Domain & HTTPS

Your domain's DNS records and your router's forwards for ports 80 and 443 must lead to this server. OurGrove then gets and renews the HTTPS certificates for you.

Allow new public HTTPS app addresses

Turning this off stops new public app addresses. Existing public apps and the public dashboard can still be reached through their saved addresses. To stop outside access immediately, remove your router forwards for ports 80 and 443. Dynamic DNS keeps updating while its provider is configured below.

Base Domain

DNS records

DNS records to create

A DNS record tells the internet which address a name leads to. Create these where you manage your domain (the company you bought it from, or your DNS provider). An A record points a name at an IPv4 address such as 203.0.113.10.

Wildcard app subdomains

Create this at your DNS provider so apps can use addresses like nextcloud.example.com.

*.example.com A your public internet address

Base domain

Optional, but useful if you also want the root domain to reach this box.

example.com A your public internet address

Contact email for certificates

Dynamic DNS (advanced: only if your internet address changes and your DNS provider gave you an update address)

Dynamic DNS

Status Not configured

Reverse Proxy Checking...

Certificates Automatic (free certificates from Let's Encrypt)

Certificate and DNS diagnostics

These checks see this server and public DNS. They cannot prove that your router forwards outside traffic correctly. Test an app address from a phone with Wi-Fi off before sharing it.

Public dashboard access

Reach this dashboard at an HTTPS address under your domain. Your existing local address stays available.

After enabling it, keep this local page open. On a phone with Wi-Fi off, open the HTTPS address below and sign in with your existing OurGrove account. If the browser warns about its certificate, return here and run HTTPS Checks. The local and public addresses may ask you to sign in separately.

Checking public dashboard access…

Bot notification feedPublishing and review reminders

Publish new server alerts to administrator MCP keys. Older alerts remain private.

Feed scope and polling

An administrator's read-only or install key can read alert titles, summaries, and next steps through list_notifications or the HTTPS feed. Non-admin keys cannot. Alerts can reveal app names, security events, and server problems. Publishing is independent of personal email choices. Configure the bot's own schedule; OurGrove does not message it.

For HTTPS polling, send Authorization: Bearer <MCP key>. Save next_after_id and pass it as after_id on the next check.

Publish notifications to bots

Remind me to review bot access every days

Reminder appears on Overview; opted-in admins also receive email.

Bot feed URL

Email Notifications

Alert choices are personal.Each administrator independently chooses which messages go to their account email address.

Enable SMTP

SMTP Host

Advanced email settings

Port

Security

Username

Password

From Email

Global Fallback Address Optional. Used only when no eligible administrator is opted in to an alert.

Dashboard HTTPS URL Required for email password recovery. Use the HTTPS address people use to open this dashboard.

Test Recipient Your account email is suggested when available. To check password recovery delivery, send to that inbox. A successful test means the mail server accepted the message, not that the inbox received it.

Save changes first. Send Test uses saved settings and does not save this form.

Loading email settings…

Password recovery emailChecking setup and recent delivery…

Android phone notifications

Get server alerts on your phone through the OurGrove Android app. Each administrator connects their own phone.

Checking phone connections…

Open this dashboard through HTTPS, then go to Network & remote access → Phone pairing and scan the QR code with the OurGrove app.
Install ntfy on the phone, connect it to your ntfy HTTPS service, and choose it as the UnifiedPush distributor.
Open Server alerts in the OurGrove app, enable Phone notifications, then choose Send test push.

Private ntfy service setup

Give a dedicated ntfy user read access to up* topics and allow anonymous write access to up* so OurGrove can publish encrypted wake-ups. Alert details are fetched directly from this server. Android checks for missed alerts when battery scheduling allows.

System Information

Version -

Hostname -

Data Directory -

Homepage Dashboard

Automatically update the Homepage tiles when apps change

Install Homepage from the app catalog, then open it from its installed app card.

Updates

Current Version -

Update Channel

Checking the current update channel…

Deployment Current

Latest Version -

Tracked Image -

Update Output

Last update log

Open Maintenance to load the update log.

Network Connection

Small connection checks run once a minute against Cloudflare and Google. Each check opens a fresh connection to catch intermittent failures. Results describe this server's internet access, not the router's internal health or a VPN client's connection.

The longer test runs 12 rounds and can take up to two minutes. Reports include timings and DNS/HTTPS failures, without response contents.

Loading network checks…

Disk Health

Loading disk health…

Daily scan at

Loading disk health…

Support & Diagnostics

One bundle for supportIncludes logs, system and Docker state, and limited app and settings summaries.

Logs may contain private details or secrets written by apps. Review the bundle and remove sensitive details before sharing it.

Host Machine Logs

Host logs not loaded yet.

OurGrove Service Logs

Service logs not loaded yet.

Docker Logs

Docker logs not loaded yet.

Network Speed Test

Measure upload, download, and ping from this appliance to the public internet.Uses the speedtest-cli package; results measure the path from the host's outbound interface, not from your browser.

Click Run Speedtest to measure your connection.

Machine deploy key

Give this public key to your repository maintainer if your OurGrove machine needs access to a private Git repository. Ask them to add it as a read-only deploy key. This key does not let someone sign in to your machine.

Server public key

Loading...

Auto-update schedule

Apply updates automatically

When off, new images are downloaded and staged automatically. Reboot when you are ready to use one.

Check every hours

Minimum 1, maximum 168 (one week). Used when no maintenance window is set. Without a window, an update can restart the server at any time of day, so set one below if that would interrupt you.

Use a daily maintenance window

Check for and download updates only in this window. If automatic application is on, the restart also happens here, so pick a time nobody is using the server. The suggested window starts after the nightly backup, which cannot overlap it.

From to

Loading…

Power Management

System Power

App Recovery CentreCheck app health, dependencies, resources, and backup readiness when needed.

Review app health, dependencies, resource pressure, saved-setting migrations, and backup readiness.

Open this section to check app recovery readiness.

Welcome to OurGrove

Initial Setup Required

Set up two-factor authentication

Save your recovery codes

Your Grove.

Checking your server…

Make your server useful.

At a glance.

Your apps

Strata AI

Server notifications

Room to grow.

CPU Usage

Memory Usage

Disk Usage

CPU Temperature

GPU History

API Health

Service Overview

Recent Health Checks

System Diagnostics

AI.

Strata AI

Connect an AI agent

Installed agents

Connect an AI agent

Installed agents

Downloaded llama.cpp models

Small starter · about 806 MB

More capable · about 3.4 GB total

On this server

Finish OpenClaw browser access

Apps.

Containers (advanced)

Runtime Containers

Backups.

Recovery points

Saved backups

Schedule and destinations

1. Keep Local Backups

2. Copy to a USB Recovery Drive

3. Copy to a NAS

4. Copy to Object Storage

One complete archive, then copies in safer places

Disks.

Space at a glance

Storage pools

Review your pool

ZFS protection and space

Where app files live

Local backup archives

Settings.

Find a setting

Local AI

Installed app storage

Data from removed apps

Appearance

Time & Region ?

Security ?

Assistant access

Connect an assistant (MCP) ?

Allow a trusted assistant to install apps

Allow server management

Pending app requests

Accounts with assistant access

Dashboard two-factor policy ?

User Management

SSH Access ?

SMB File Sharing ?

App Shares

Server IP Address ?

Domain & HTTPS

DNS records to create

Public dashboard access ?

Email Notifications ?

Android phone notifications

System Information

Homepage Dashboard ?

Updates

Network Connection

Time & Region

Security

Connect an assistant (MCP)

Dashboard two-factor policy

SSH Access

SMB File Sharing

Server IP Address

Public dashboard access

Email Notifications

Homepage Dashboard