# SynchronizeGroups

This action searches a repository for group updates and sends these updates to OmniGroupServer.

Type: Asynchronous

Parameter Name | Description | Required
--- | --- | ---
`Config` | A base-64 encoded configuration. The configuration parameters that are set override the same parameters in the connector's configuration file. | No
`TaskSections` | The names of the task sections to use to perform synchronization. If this parameter is unspecified, all configured task sections are used. The sections must include the `GroupServerHost` and `GroupServerPort` parameters as a minimum, in addition to any connector-specific parameters. | No
`SecurityInfo` | An IDOL security info string. Set this parameter to impersonate the specified user. To impersonate another user you must set DocumentSecurityType and SecurityInfoKeys. | No
`Override_Config_Parameters` | Any other action parameters that you set override settings in the connector's configuration file. For example:
    /action=fetch&fetchaction=...
                 &[Section]Parameter=Value
where `[Section]` (optional) is the name of a configuration file section, `Parameter` is the name of a configuration parameter, and `Value` is the parameter value. | No

## Example

    http://host:port/action=Fetch&FetchAction=SynchronizeGroups

## Response

A sample response appears below. In this example, two tasks were performed as part of the synchronize groups (GROUPS1 and GROUPS2).

    <action>
      <fetchaction>SYNCHRONIZEGROUPS</fetchaction>
      <tasks>
        <success>GROUPS1</success>
        <success>GROUPS2</success>
      </tasks>
      <token>MTAuMi4xMDUuMzQ6MTIzNDpGRVRDSDoxNDAyOTU3MzY4</token>
      <status>Finished</status>
      <queued_time>2009-Oct-15 14:44:32</queued_time>
      <time_in_queue>0</time_in_queue>
      <process_start_time>2009-Oct-15 14:44:32</process_start_time>
      <time_processing>3</time_processing>
      <process_end_time>2009-Oct-15 14:44:35</process_end_time>
    </action>

If a SynchronizeGroups task does not complete successfully, the task name appears between `<failed>` tags and a message explains the reason for the failure:

    <tasks>
       <failed message="Error message">MyTask1</failed>
    </tasks>

_FT_HTML5_bannerTitle.htm