You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When reviewing the tables, we found that ROHQ doesn't have the concept of a queue owner, every host appears to have the same level of permissions. I'm not sure how important this is but it's something that should be discussed.
This poses 2 potential issues I can think of:
Any host could delete a queue that they are added to. Queue recovery is possible but I believe it requires support to handle. I don't know how often this happens.
When exporting queue details (new feature) every host is given the information for every other host. Since we don't know who is the "owner", who would be the person who should have access to information on all other hosts, it's shared between everyone. I don't know how important this is.
Adding a column to capture the "owner" or "creator" would resolve this issue going forward though I don't know how this would be assigned for past queues.
We'd likely have to have some consideration for passing over the ownership to someone else if someone leaves the university. I'm not sure how that would work. Maybe just in the admin UI would be enough.
The text was updated successfully, but these errors were encountered:
When reviewing the tables, we found that ROHQ doesn't have the concept of a queue owner, every host appears to have the same level of permissions. I'm not sure how important this is but it's something that should be discussed.
This poses 2 potential issues I can think of:
Adding a column to capture the "owner" or "creator" would resolve this issue going forward though I don't know how this would be assigned for past queues.
We'd likely have to have some consideration for passing over the ownership to someone else if someone leaves the university. I'm not sure how that would work. Maybe just in the admin UI would be enough.
The text was updated successfully, but these errors were encountered: