Provide a mechanism to create admin and read only users in HyperDx
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9.9k
- Forks
- 471
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 117
Description
I have read the previously raised issues on HyperDx for RBAC and SSO requirements and it is overlapping for enterprise features. Can we at least have a division of HyperDx in two roles i.e. admin and read-only.
admin
- Entire settings section, CRUD operations for dashboards, alerts etc
- allow admin permissions for a specific folder which has dashboards
read-only
- this user(s) group to be allowed to do CRUD operations on specifically selected dashboard folder. Something like a playground.
- can read only alerts and other dashboards
This way it can be safely added to any org wide usage where even accidentally nobody makes any changes to important entities.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the previously raised RBAC and SSO issues referenced in the message, then map the proposed admin and read-only roles to settings, dashboards, alerts, and folder permissions. Done should mean a settled permission model that supports organization-wide protection while allowing the specified dashboard-folder playground, with access rules verified for both roles.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100