What should be defined to ensure that group members can access vRealize Operations objects when importing a group from Active Directory into vRealize Operations?

Question

Options

• ADescription
• BRole
• CGroup Members
• DType

• A
  4% (1)
• B
  88% (21)
• C
  8% (2)

Explanation

When importing an Active Directory group into vRealize Operations, a Role must be assigned to define what permissions group members have over vRealize Operations objects (such as dashboards, resources, and policies). Without a role, the imported group exists in the system but has no access rights to any objects, making role assignment the critical step for enabling meaningful access.

A (Description) is simply a free-text field for documentation - it has no bearing on what objects a user can see or interact with. C (Group Members) are already defined within Active Directory itself; vRealize Operations pulls membership from AD automatically and does not require you to manually specify members during import. D (Type) identifies the authentication source type (e.g., AD, LDAP), which is configured at the import source level, not as a permission control for object access.

Memory tip: Think "Role = Rights." Any time you're granting access in vRealize Operations - whether to a user or an imported group - assigning a Role is always the step that translates group membership into actual object-level permissions.

No community discussion yet for this question.