Users & Access Control — DevMonk Connect

What is it?

Give people access without giving them everything

Sharing server access is risky if everyone has root-level control. DevMonk's user system lets you create separate accounts for each person with exactly the permissions they need. An owner can do anything. An admin can manage most things. A viewer can look but not touch. This is called "role-based access control" — a fancy name for a simple idea.

Action	Owner	Admin	Viewer
View dashboard, status, logs	Yes	Yes	Yes
Use terminal, files, docker	Yes	Yes	No
Manage services / proxy	Yes	Yes	No
Add / remove non-owner users	Yes	Yes	No
Change owner settings / delete owner	Yes	No	No

Use Cases

Why use Users & Access Control?

🕵️

Check logs without making changes

Give a colleague a viewer account — they can see status and logs but can't break anything.

🤖

Create a deploy-bot account

Automated systems get their own account with a unique password — easy to revoke if needed.

👔

Give a client read-only monitoring

Clients can see their app's status and uptime without any ability to change your server.

🔑

Rotate compromised credentials

If an account's password leaks, disable or change it instantly without touching the others.

Before You Start

Requirements checklist

✔Logged in as owner or admin

✔DevMonk agent running

Step-by-Step

How to add and manage users

1

Open DevMonk → Users page

Click "Users" in the sidebar. You'll see a list of all current accounts.

┌────────────────────────────────────────────┐ │ USERS [ + Add User ] │ │ ────────────────────────────────────── │ │ you@home owner [ Edit ] │ │ alice admin [ Edit ] [ Del ] │ │ monitor-bot viewer [ Edit ] [ Del ] │ └────────────────────────────────────────────┘

2

Click "+ Add User"

Fill in the username, password, and choose a role: owner, admin, or viewer.

┌──────────────────────────────────────┐ │ Add User │ │ Username: [ alice ] │ │ Password: [ ************ ] │ │ Role: [ admin ▾ ] │ │ [ Create User ] │ └──────────────────────────────────────┘

3

Share credentials with the new user

Give them your DevMonk URL and their username/password. They log in and see only what their role allows.

4

Edit or remove users anytime

Click Edit to change their role or reset their password. Click Delete to revoke access instantly.

1

Same steps — Users page is identical on VPS

Navigate to your DevMonk URL → Users → Add User. The interface and functionality are identical whether you're on a home PC or a cloud server.

2

For VPS: consider creating a viewer for clients

If you're hosting something for a client, create a viewer account for them. They get read-only access to your DevMonk dashboard — status, uptime, logs — but nothing else.

Try it now

Create a viewer account

Go to the Users page in DevMonk, click Add User, and create a new account with the "viewer" role. Then open an incognito window and log in as that user to see what they can (and can't) access.

# Navigate in DevMonk:
Dashboard → Users → + Add User → Role: viewer → Create

Common Questions

FAQ

Yes. Click Edit next to any user and change their role from the dropdown. The change takes effect immediately — their next page load will reflect the new permissions.

Yes. Click Edit on any user account and set a new password. The user's existing session tokens are invalidated, so they'll need to log in again with the new password.

Viewers can see: system status overview, container statuses and logs (read-only), service list and their status, and the audit log. Viewers cannot: use the terminal, upload/modify files, start/stop containers, manage services, or access VPN settings.

Yes. Admins can create and manage any account except the owner account. They can create other admins, viewers, and lower-level accounts. Only the owner can modify or create other owner-level accounts.

Next Steps

Explore related features