This article provides guidance on common items to review when using Okta Identity Governance Access Requests, where a configured task assigned to Group Owner(s) becomes unassigned or is not assigned to all expected Group Owners.

In the case where the Requester is also a Group Owner that is set for the Task, resulting in a self-approval situation, also see Access Request Expected Reviewer Self-Attestation Behavior.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Okta Identity Governance (OIG)
• Access Requests
• Request Types
• Resource Centric Access Requests (RCAR)

What should be checked when an approval task is unassigned or not assigned as expected for a Request Type based Request?

NOTE: This does not apply to Resource Centric Access Requests (RCAR), as Just In Time (JIT) logic is used for similar scenarios with RCAR.

• For Group or Individual assigned as Group Owner:

  • Make sure the user(s) are assigned to the Okta Access Requests app.

• If Group Owner is: Group assigned as Group Owner

  • If the owner of a group in Okta is another Okta group, this group must be pushed to Access Requests for it to be used as an approver.
    • Example: 

• If the Group Owner is: individual user(s) assigned

  •  If the User was recently added as an "Individual" Group Owner and the daily group synchronization has not occurred, manually synchronize the groups from the Access Requests Console settings:
    1. Navigate to the Access Requests Console, select Settings, choose the Resources tab, and select Okta Groups.
    2. Click Update Now in the top right corner.
    3. Refresh the page and verify that the Last updated value reflects the current time.
    4. Create the request again.

What should be checked when the intended group’s owner(s) are missing from a Request Type or RCAR approval task?

• Verify that the user(s) are assigned as Group (Resource) Owner for the intended Group.

Review the assignment limits and expected behaviors for Group Owner assigned Tasks for Request Types and RCAR (Conditions/Sequences).

• Limit of 25 Random Users assigned to a task/question:
  • As with the Okta Group selection, there is a limit of 25 "random" users that can be assigned as approvers when using Group Owner.
• Group Owner with People(individual) and Group Assignments:
  • If a group owner has a mix of People(individual) and Group assignments, as of Release 2026.06.0, Okta now assigns access request tasks to both, the individual users and the members of the owner group.

Related References

• How to See Addition/Removal of Group Owners via System Log Event 
• Access Requests
• Access Request Assignee Types
• Resource Centric Access Requests (RCAR)