Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple feature requests/discussion with the maintainers and community #5665

Open
2 tasks done
SharkyND opened this issue Feb 27, 2025 · 0 comments
Open
2 tasks done
Labels

Comments

@SharkyND
Copy link

⚠️ Please verify that this question has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

Hi Maintainers,

I really like this project and want to discuss on brining in some new features that will help with the adoptibality on it. Some features that we think would help organizations:

  • SSO implementation (Feature already requested: SSO Provider Support for Uptime Kuma Login #5589)
  • Introduction of Roles - initially there will be three heirachies i.e. SuperAdmin, TeamAdmin, User (Can only see dashboard). This Teams will be another layer, that can have different monitor groups, status pages etc under each Team
  • Calendar view for history and upcoming maintenances
  • Moving of maintenance under each monitor in the dashboard view for visibility.

Are any of these ideas in the backlog for 2.x? Would the community be interested in the contribution of these features? If yes, how can I suggest the addition to the roadmap, and contribute the code.

Thanks.

📝 Error Message(s) or Log

No response

🐻 Uptime-Kuma Version

2.x.x

💻 Operating System and Arch

NA

🌐 Browser

NA

🖥️ Deployment Environment

  • Runtime: NA
  • Database: NA
  • Filesystem used to store the database on: NA
  • number of monitors: NA
@SharkyND SharkyND added the help label Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant