mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
create another account #798
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#798
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 @W3T3R4NN on GitHub (Feb 3, 2022).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
Other
🔖 Feature description
another users can create another acount in website. This user can see their own uptimes and can create dashboard
✔️ Solution
another users can create another acount in website. This user can see their own uptimes and can create dashboard
❓ Alternatives
No response
📝 Additional Context
No response
@Appoxo commented on GitHub (Feb 3, 2022):
+1
@darks00ul commented on GitHub (Feb 13, 2022):
+1
@TLeM4 commented on GitHub (Mar 3, 2022):
+1
Alternative solution (for now) is to create another user in db
@thompol commented on GitHub (Mar 5, 2022):
Possible duplicate of #128
@adiastra commented on GitHub (Aug 26, 2022):
I am unclear if this has been implemented but I would really like this feature. Aven basic multi user functionality would be a great place to start
@CommanderStorm commented on GitHub (Dec 3, 2023):
@W3T3R4NN
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.