Skip to main content

Assigning Management Roles Needed to Access Resource Admin

EmpowerID employs Management Roles to control access to Resource Admin, a microservice for managing various resources (such as applications, groups, and shared folders). These Management Roles ensure users can access only the parts of the Resource Admin microservice that are relevant to their responsibilities.

Resource Admin Management Roles are categorized into two types:

  1. UI-* Management Roles — Provide access to the application's user interface (UI) components, including pages, controls, workflows, and reports.
  2. VIS-Res-Admin-MS-API Management Role — Grants access to the APIs used by the Resource Admin microservice.
Required Role Combinations

A user must be granted both the relevant UI-* role(s) and the VIS-Res-Admin-MS-API role to use all aspects of the microservice. Additionally, they must have any required activity (ACT-<Resource>-) and visibility (VIS-<Resource>-) roles applicable to the persona they use in Resource Admin.

Example: If a user needs to manage shared folders, they will require:

  • A UI role for shared folders (e.g., UI-Res-Admin-MS-Shared-Folders)
  • The VIS-Res-Admin-MS-API role
  • Corresponding ACT and VIS Management Roles for shared folders

Resource Admin Management Roles

To manage resources in Resource Admin, users need one or more of the following Management Role assignments (based on their required scope).

Management RoleRole TypeDescription
UI-Res-Admin-MS-ApplicationFeature Set (UI)Provides access to the Resource Admin UI for managing applications. This role grants access to:

  • User Interface Controls: Grants Viewer access to application management controls, including Azure application management, app roles, role definitions, token configurations, and more.
  • Pages and Reports: Access to application details pages, token configurations, and application listing pages.
  • Web Services: Executor access to services including ListDataItem, AzureTenantView, RequestWorkflowView, OrgZoneView, and AssigneeView.
  • Workflows: Initiator access to workflows for managing Azure applications, including create, edit, delete operations, client secrets, certificates, scopes, app roles, and API permissions.

This role provides comprehensive access to all application management features in Resource Admin.
UI-Res-Admin-MS-Application BaseFeature Set (UI)This least privilege role provides basic access to the Resource Admin UI for managing applications. Grants limited access to:

  • User Interface Controls: Essential controls for viewing and basic application management.
  • Pages and Reports: Core application pages and reports.
  • Web Services: Essential web services for application operations.
  • Applications: Basic application access permissions.

Use this role for users who need read-only or minimal application management capabilities.
UI-Res-Admin-MS-Application-ClaimsMapping-PolicyFeature Set (UI)Provides access to Resource Admin UI for managing Azure Claims Mapping Policies. Grants access to:

  • User Interface Controls: Controls specific to Claims Mapping Policy management.
  • Pages and Reports: Claims Mapping Policy pages and reports.
  • Workflows: Workflows for creating, editing, and managing Claims Mapping Policies.
UI-Res-Admin-MS-CommonFeature Set (UI)Provides access for common/shared UI used by the Resource Admin microservice. The role specifically grants Viewer access to the Resource Admin Microservice application.

This role is typically assigned in combination with other resource-specific roles to provide access to shared interface components.
UI-Res-Admin-MS-GroupsFeature Set (UI)Provides access to Resource Admin UI for managing Groups. Grants access to:

  • User Interface Controls: Controls for group management including member management, group attributes, and access assignments.
  • Pages and Reports: Group listing pages, group details pages, and group-related reports.
  • Workflows: Workflows for creating, editing, and managing groups.
UI-Res-Admin-MS-Groups-BaseFeature Set (UI)This least privileged role provides basic access to Resource Admin UI for managing groups. Grants limited access to:

  • User Interface Controls: Essential controls for viewing and basic group operations.
  • Pages and Reports: Core group pages and reports.
  • Web Services: Essential web services for group operations.
  • Applications: Basic group-related application access.

Use this role for users who need read-only or minimal group management capabilities.
UI-Res-Admin-MS-MailboxesFeature Set (UI)Provides access to Resource Admin UI for managing Mailboxes. Grants access to:

  • User Interface Controls: Controls for mailbox management including mailbox settings, permissions, and configurations.
  • Pages and Reports: Mailbox listing pages, mailbox details pages, and mailbox-related reports.
  • Workflows: Workflows for creating, editing, and managing mailboxes.
UI-Res-Admin-MS-Mailboxes-BaseFeature Set (UI)This least privileged role provides basic access to Resource Admin UI for managing mailboxes. Grants limited access to:

  • User Interface Controls: Essential controls for viewing and basic mailbox operations.
  • Pages and Reports: Core mailbox pages and reports.
  • Web Services: Essential web services for mailbox operations.

Use this role for users who need read-only or minimal mailbox management capabilities.
UI-Res-Admin-MS-Management-RoleFeature Set (UI)Provides access to the Resource Admin UI for managing Management Roles. Grants access to:

  • User Interface Controls: Controls for Management Role administration including membership management, access assignments, and role configurations.
  • Pages and Reports: Management Role listing pages, role details pages, and role-related reports.
  • Web Services: Web services required for Management Role operations.
UI-Res-Admin-MS-Management-Roles-BaseFeature Set (UI)This least privilege role provides basic access to the Resource Admin UI for managing Management Roles. Grants limited access to:

  • User Interface Controls: Essential controls for viewing and basic Management Role operations.
  • Pages and Reports: Core Management Role pages and reports.

Use this role for users who need read-only or minimal Management Role access.
UI-Res-Admin-MS-PeopleFeature Set (UI)Provides access to Resource Admin UI for managing People. Grants access to:

  • User Interface Controls: Controls for people management including user attributes, lifecycle operations, and organizational assignments.
  • Pages and Reports: People listing pages, person details pages, and people-related reports.
  • Workflows: Workflows for onboarding, editing, and managing people records.
UI-Res-Admin-MS-People-BaseFeature Set (UI)This least privileged role provides basic access to Resource Admin UI for managing people. Grants limited access to:

  • User Interface Controls: Essential controls for viewing and basic people operations.
  • Pages and Reports: Core people pages and reports.
  • Web Services: Essential web services for people operations.

Use this role for users who need read-only or minimal people management capabilities.
UI-Res-Admin-MS-Shared-FoldersFeature Set (UI)Provides access to the Resource Admin UI for managing Shared Folders. Grants access to:

  • User Interface Controls: Controls for shared folder management including permissions, access managers, and folder configurations.
  • Pages and Reports: Shared folder listing pages, folder details pages, and folder-related reports.
  • Web Services: Web services required for shared folder operations.
UI-Res-Admin-MS-Shared-Folders-BaseFeature Set (UI)This least privileged role provides basic access to Resource Admin UI for managing shared folders. Grants limited access to:

  • User Interface Controls: Essential controls for viewing and basic shared folder operations.
  • Pages and Reports: Core shared folder pages and reports.

Use this role for users who need read-only or minimal shared folder management capabilities.
VIS-Res-Admin-MS-APIVisibility (VIS)Required for all Resource Admin users. Provides access to the base web services required by all users of the Resource Admin microservice.

This role must be assigned in combination with at least one UI-* role to enable Resource Admin functionality.

Quick Reference: Role Capabilities

This table provides a quick overview of capabilities granted by each resource-specific role pair.

Resource TypeViewCreateEditDeleteManage MembersFull Feature Set RoleBase Role
ApplicationsN/AUI-Res-Admin-MS-ApplicationUI-Res-Admin-MS-Application-Base
GroupsUI-Res-Admin-MS-GroupsUI-Res-Admin-MS-Groups-Base
Management RolesUI-Res-Admin-MS-Management-RoleUI-Res-Admin-MS-Management-Roles-Base
PeopleN/AUI-Res-Admin-MS-PeopleUI-Res-Admin-MS-People-Base
MailboxesN/AUI-Res-Admin-MS-MailboxesUI-Res-Admin-MS-Mailboxes-Base
Shared FoldersUI-Res-Admin-MS-Shared-FoldersUI-Res-Admin-MS-Shared-Folders-Base
Required Common Roles

All users must also have VIS-Res-Admin-MS-API and UI-Res-Admin-MS-Common roles in addition to their resource-specific roles.

Viewing Resource Admin Management Roles

EmpowerID allows you to view all Management Roles the Resource Admin microservice uses. Follow these steps:

  1. In the navbar of the EmpowerID Web app, go to Apps and Authentication > Applications.
  2. On the Applications tab, search for Resource Admin Microservice App and click the Display Name link for the app. Searching for Resource Admin Microservice App Searching for the Resource Admin Microservice App in the Applications view
  3. This opens the View One page for the microservice, allowing you to view and manage relevant objects in EmpowerID. Resource Admin View One Page View One page showing Resource Admin microservice details
  4. Select the App Resources tab and expand the Management Roles Used By This Application section. Management Roles Used By This Application Management Roles list showing all roles associated with Resource Admin You will see a list of all Management Roles associated with the Resource Admin microservice.

Role Assignment Best Practices

When assigning Resource Admin Management Roles, consider the following best practices:

Choose the Appropriate Access Level

  • Full Access Roles (e.g., UI-Res-Admin-MS-Application): Assign to users who need comprehensive management capabilities.
  • Base Roles (e.g., UI-Res-Admin-MS-Application Base): Assign to users who need read-only or limited management capabilities.

Combine with Required Supporting Roles

Always ensure users have:

  1. At least one UI- role* for the resources they manage
  2. The VIS-Res-Admin-MS-API role (required for all users)
  3. Appropriate ACT and VIS roles for the specific resources they manage

Example Role Combinations

Application Administrator:

  • UI-Res-Admin-MS-Application (full application management)
  • VIS-Res-Admin-MS-API (API access)
  • UI-Res-Admin-MS-Common (shared UI components)
  • Relevant ACT-Application-* and VIS-Application-* roles

Group Administrator (Read-Only):

  • UI-Res-Admin-MS-Groups-Base (limited group access)
  • VIS-Res-Admin-MS-API (API access)
  • UI-Res-Admin-MS-Common (shared UI components)
  • Relevant VIS-Group-* roles

Multi-Resource Administrator:

  • Multiple UI-* roles for different resource types
  • VIS-Res-Admin-MS-API (API access)
  • UI-Res-Admin-MS-Common (shared UI components)
  • Corresponding ACT and VIS roles for each resource type

Assigning Management Roles to Users

To assign Resource Admin Management Roles to users, follow the standard EmpowerID role assignment process:

  1. Navigate to the user's profile in EmpowerID
  2. Access the Management Roles section
  3. Assign the appropriate combination of roles based on the user's responsibilities
  4. Verify the user has access to Resource Admin by having them log in and test their permissions
Testing Access

After assigning roles, have users verify their access by:

  1. Logging into Resource Admin
  2. Confirming they can see the appropriate resource types in the dropdown
  3. Testing that they can perform the expected operations on resources

Troubleshooting Role Assignments

Use this section to diagnose and resolve common role assignment issues.

User Cannot Access Resource Admin

Symptom: User cannot access Resource Admin at all; receives access denied error or cannot see the application

Possible Causes and Solutions:

  1. Missing Common Roles

    • Check: Verify user has both UI-Res-Admin-MS-Common and VIS-Res-Admin-MS-API roles
    • Solution: Assign both required common roles
  2. No Resource-Specific Roles

    • Check: Confirm user has at least one UI-Res-Admin-MS-* role (e.g., Groups, People, Applications)
    • Solution: Assign appropriate resource-specific role based on user's responsibilities
  3. Role Assignment Not Yet Effective

    • Check: Verify when roles were assigned
    • Solution: Have user log out and log back in, or wait for role propagation (typically 5-15 minutes)

User Cannot See Specific Resource Type

Symptom: Resource type missing from the Resource Type dropdown menu

Possible Causes and Solutions:

  1. Missing Resource-Specific UI Role

    • Check: Verify user has the appropriate UI-Res-Admin-MS-<Resource> or UI-Res-Admin-MS-<Resource>-Base role
    • Solution: Assign the required UI role for that resource type
  2. Missing Supporting VIS Roles

    • Check: Confirm user has corresponding VIS-<Resource>-* roles
    • Solution: Assign visibility roles that match the resource scope
  3. No Resources in Scope

    • Check: Verify the user owns or has visibility to resources of that type
    • Solution: Either assign ownership of resources or expand visibility scope through appropriate VIS roles

User Can See Resources But Cannot Perform Actions

Symptom: Resources are visible in the list but action buttons are disabled or workflows cannot be initiated

Possible Causes and Solutions:

  1. Using Base Role Instead of Full Role

    • Check: Determine if user has -Base role (e.g., UI-Res-Admin-MS-Groups-Base)
    • Solution: If user needs full management capabilities, upgrade to the full feature set role (e.g., UI-Res-Admin-MS-Groups)
  2. Missing Activity (ACT) Roles

    • Check: Verify user has required ACT-<Resource>-* activity roles for the desired operations
    • Solution: Assign appropriate activity roles (e.g., ACT-Group-Create, ACT-Group-Modify)
  3. Resource Ownership Restrictions

    • Check: Confirm whether the user owns the resource or has delegated rights
    • Solution: Either assign ownership of the resource or configure delegation boundaries to include the resource
  4. Insufficient Delegation Boundaries

    • Check: Review user's delegation scope and boundaries
    • Solution: Adjust delegation settings to include the target resources

User Sees Too Many Resources

Symptom: User can see resources outside their area of responsibility

Possible Causes and Solutions:

  1. Overly Broad VIS Roles

    • Check: Review assigned VIS-* roles for scope
    • Solution: Replace organization-wide visibility roles with location or department-specific roles
  2. Incorrect Use of Full Access Role

    • Check: Determine if user has full feature set role when they only need base access
    • Solution: Replace with corresponding -Base role if read-only access is sufficient
  3. ResAdmin Mode Not Configured


Workflows Complete But Changes Not Reflected

Symptom: User initiates workflows successfully, but resources remain unchanged

Possible Causes and Solutions:

  1. Approval Pending

    • Check: Review the workflow approval status
    • Solution: Inform user that changes require approval; check with approvers
  2. Workflow Errors

    • Check: Review workflow logs for errors
    • Solution: Address any system connectivity issues or permission problems on target systems
  3. Target System Synchronization Delay

    • Check: Verify synchronization schedule for the affected account store
    • Solution: Wait for next sync cycle or manually trigger synchronization if needed