Group push operations

Group Push (GP) allows admins to take ownership of third-party, target apps in Okta. This is done by either pushing Okta groupsGroups allow you to organize your end users and the apps they can access. Assigning apps to large sets of end users is made easier with groups. to target apps (GP) or by using enhanced Group Push (GPE) to import groups from target apps and linking them to Okta. The table below details the supported operations and how they appear in Okta.

 

Operations Description
Create a mapping for a new group (GP) Group A is a group created in Okta, and does not exist in the target appAn abbreviation of application. Essentially, it is a web-based site used to perform any number of specific tasks, and requires authentication from end users by signing in.. When GroupA is pushed from Okta to the target app, an instance of the group is created in the app.
Create a mapping for an existing group (GPE)

Group B is a group created in the target app, then imported to Okta. Group A is created in Okta to link to Group B. Group A is the group that appears on the Okta Groups page. Once linked, Group B is Okta mastered. Group B does not appear on the Okta Groups page.

In this scenario, Renaming is turned ON.

Group B is a group created in the target app, then imported to Okta. Group A is created in Okta to link to Group B. Both groups appear on the Okta Groups page. Once linked, Group B is Okta mastered.

In this scenario, Renaming is turned OFF.

Unlink and delete a group in the target app (GP) Group A is a group that exists both in Okta and the target app. When Group A is unlinked from the target app, it still remains in Okta, but is deleted in the target app.
Unlink and leave a group in the target app (GPE) Group B is a group created in the target app, then imported to Okta. Group A is created in Okta to link to Group B. When unlinked, all memberships and references in Group A are deleted in Okta. Group B appears like any other imported group

Top