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

Default alert filter for user or role #501

Open
satterly opened this issue Nov 13, 2021 · 0 comments
Open

Default alert filter for user or role #501

satterly opened this issue Nov 13, 2021 · 0 comments
Labels
enhancement New feature or request priority: low A problem affecting a non-core component
Milestone

Comments

@satterly
Copy link
Member

satterly commented Nov 13, 2021

Stephane @steevivo Nov 20 21:27
@satterly Hi Nick , I have a question about multi user with a separate alarm access group , for example one of this access to the network alarm and another acces to the dedicated application X , is it possible ?

Nick Satterly @satterly Nov 21 15:29
@steevivo the only way to do this at the moment is to enable customer views and create a "customer" for network and a "customer" for application X.
Not ideal. especially . But the only way I can think this might work currently.

Nick Satterly @satterly Nov 21 19:34
Try using a queue not a topic.
@steevivo one question. Is this simply a default filter of visible alerts per user, or is there an additional layer of authorization that you are seeking here? ie. is it ok if the user modifies the filter themselves to see other alerts or would you expect that these are the only alerts they should have access to?
that’s actually two questions. or one question with a follow-up question to clarify :)

Stephane @steevivo 21:23
@satterly yes Nick, a simply default filter of visible alerts per user and in my case a group of users

Nick Satterly @satterly 22:06
@steevivo ok. that’s good to know. i would have been reluctant to add yet another layer of authorization. i can’t promise anything but i’ll put it on the backlog. thanks for your feedback.

@satterly satterly added enhancement New feature or request priority: medium A problem affecting a core component for which there is a workaround priority: low A problem affecting a non-core component and removed priority: medium A problem affecting a core component for which there is a workaround labels Nov 13, 2021
@satterly satterly added this to the Release 9 milestone Dec 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority: low A problem affecting a non-core component
Projects
Status: 🧊 Ice Box
Development

No branches or pull requests

1 participant