Create sub set for an other organization.
Not plannedIn a time that organizations out source there hardware management it maybe is helpful to provide an subset so the administrator will have an overview what the impact will be when a major / critical incident happens.
-
Official comment
Hi Gertjan Rieke,
Thank you for the update. I will close this post.
Please feel free to submit a new post if the requirement surfaces in the future.
Thanks,
Team ValueBlue
-
Hi Gertjan Rieke,
Thanks for your feedback! Really appreciate it. I will discuss this in the next feedback session.
0 -
Hi Gertjan Rieke,
Sorry that I kept you waiting, but because of the holidays, the feedback session was canceled.
I discussed it in this week's session, but this wish is unclear. Could you provide more information? Answer the following questions would be really helpful:
- What is your wish?
- Why do you want this wish?
- Do you have a workaround? And if so, what is it?
- How would you ideally solve the problem?
- How big is the wish on a scale from 1 to 5? (1 = it would be nice, but definitely not necessary, and 5 = I cannot work another day without it).
It's much easier for us to address a wish if we clearly understand the context of the wish and why it matters to you.
Thank you in advance!
0 -
Hi Kim,
- We want to create a subset of our hardware because of the management of this hardware by a third party. In this way they can determine the impact of an incident.
- We want this because of the movement to outsource a lot of our hardware management to third party's
- The work around is to allow the third party to use Bluedolphin. This is not desirable because they see things we don't want them to see / know
- Creation of subsets for every third party we have contracted
- 4
If you like to have more info you can contact me: +31629035889
Sincerly
Gertjan Rieke0 -
Hi Gertjan Rieke,
Could this be a use case for business units?
https://valueblue.zendesk.com/hc/en-us/articles/4981782551570-Business-units
0 -
Hi Ameya,
The issue is not relevant for us anymore because of a take over of our organisation.
Sincerly
Gertjan Rieke0
Post is closed for comments.
Comments
6 comments