mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Option to add other users #648
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#648
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @funky123 on GitHub (Dec 10, 2021).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
UI Feature, Other
🔖 Feature description
You should add the option to add other user accout to view details from status-page e.g. the value of dns checks or the ping delays/history.
✔️ Solution
Adding the UI Feature for the logged-in admin User to add new users via E-Mail or simple username and password as "Viewer" only.
❓ Alternatives
implement a user-rights-management
📝 Additional Context
If there is feature already (and i can't find
@J000K3R commented on GitHub (Dec 28, 2021):
That were great if i can add more Admins or Viewer Only Users.
Please add this Feature.
@gruessung commented on GitHub (Jan 5, 2022):
Yes, this would be very helpful.
@hteibler commented on GitHub (Jan 16, 2022):
@koen20 commented on GitHub (Mar 30, 2022):
Duplicate of #128
@CommanderStorm commented on GitHub (Jun 29, 2023):
@funky123 I think this is a duplicate of #128
Duplicates only hurt issue discoverability and lead to zombies, could you either
@CommanderStorm commented on GitHub (Dec 3, 2023):
@funky123
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in #128 as there is no functional difference
⇒ I am going to close this as a duplicate.