4 results found

1. Admin Users able to assume user roles

   We have the ability for DoiT to assume roles of users in an Organization.

   A customer wants to be able to assume the roles of users, so they can see what their user is seeing.

   Cloudhealth is able to do this.

   10 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Users & Roles  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Future Consideration  ·  AdminSebastian Caparroz (Admin, DoiT) responded

   This will be handy and make sense once we have multi tenancy. We'll come back to this ticket once we're ready with it.

2. Restrict Support Case Creation by Cloud Account or Service

   I noticed that there is currently no way to limit which cloud accounts or services a user can create support cases for.

   For example, in an organization with multiple teams:

   A user from Team A should only be able to create support cases for the cloud accounts or services owned by Team A.

   However, today, that same user can open support cases for any cloud account or service across the organization.

   While DoiT Organizations can scope access for Cloud Analytics, this scoping does not apply to Support, and there is currently no workaround. As a result, users can unintentionally or incorrectly create support cases for resources they do not own.

   This capability would be especially valuable for enterprise customers, where governance and compliance are critical. Beyond controlling what actions users can take, there is also a strong need to control what resources they can see and interact with. Proper segregation of duties is a common compliance requirement, and this feature would help organizations meet those standards more effectively.

   Having the ability to restrict support case creation by cloud account and/or service would greatly improve governance, reduce confusion, and align better with enterprise operational models.

   I noticed that there is currently no way to limit which cloud accounts or services a user can create support cases for.

   For example, in an organization with multiple teams:

   A user from Team A should only be able to create support cases for the cloud accounts or services owned by Team A.

   However, today, that same user can open support cases for any cloud account or service across the organization.

   While DoiT Organizations can scope access for Cloud Analytics, this scoping does not apply to Support, and there is currently no workaround. As a result, users can unintentionally or… more

   •  

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Users & Roles  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering More Feedback  ·  AdminFrancisco (Admin, DoiT) responded

   We'll work on this idea and then prioritize.

3. Restrict Support Case Creation by Cloud Account or Service

   I noticed that there is currently no way to limit which cloud accounts or services a user can create support cases for.

   For example, in an organization with multiple teams:

   A user from Team A should only be able to create support cases for the cloud accounts or services owned by Team A.

   However, today, that same user can open support cases for any cloud account or service across the organization.

   While DoiT Organizations can scope access for Cloud Analytics, this scoping does not apply to Support, and there is currently no workaround. As a result, users can unintentionally or incorrectly create support cases for resources they do not own.

   This capability would be especially valuable for enterprise customers, where governance and compliance are critical. Beyond controlling what actions users can take, there is also a strong need to control what resources they can see and interact with. Proper segregation of duties is a common compliance requirement, and this feature would help organizations meet those standards more effectively.

   Having the ability to restrict support case creation by cloud account and/or service would greatly improve governance, reduce confusion, and align better with enterprise operational models.

   I noticed that there is currently no way to limit which cloud accounts or services a user can create support cases for.

   For example, in an organization with multiple teams:

   A user from Team A should only be able to create support cases for the cloud accounts or services owned by Team A.

   However, today, that same user can open support cases for any cloud account or service across the organization.

   While DoiT Organizations can scope access for Cloud Analytics, this scoping does not apply to Support, and there is currently no workaround. As a result, users can unintentionally or… more

   •  

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Users & Roles  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Use Organizations to manage reports

   Customer is using the multi organizational features and would like for the admins to be able to create reports and share them to specific organizations with in their tenant. This would allow them to easily create reports for the individual org and share them out to the correct groups of users.

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   In Backlog  ·  3 comments  ·  Users & Roles  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating