About file sync between SharePoint and Jive
Connecting a Jive place (group, project, space) to SharePoint can be done in two ways.
You can connect a Jive place with SharePoint as follows:
-
Connecting a place to SharePoint and creating a new site in SharePoint that syncs to the Jive place.
Permissions sync from the Jive Place to the SharePoint Site as follows:
- The Jive-Admins Permission Group(s) you have specified in the connection are added as an admin to each site created. This can be used for SharePoint admin users group or a specific user.
- The Jive-All-Users Permission Group(s) simulates the All Registered Users group in Jive. This can also be set up for specific groups.
-
Connecting a Place to an existing SharePoint site.
SharePoint permissions remain unchanged.
Groups
| Group type | All registered users in Jive | Everyone principal in SharePoint |
|---|---|---|
| Open | Granted contribute | Added to Jive Contributors permission group |
| Members only | Granted read-only | Added to Jive Readers permission group |
| Private and Private Unlisted | No permission | No permission |
Projects
Projects inherit permission from the parent place. For example, if the project is under a members-only group, the Jive-All-Users Permission Groups are added to the Jive Readers permission group.
Ongoing sync
When a user joins or is added to a group, the SharePoint user that is mapped with the Jive user is added to the SharePoint site connected to the group. Similar behavior occurs when a user leaves or is removed from a group — the user is removed from the SharePoint site as well.
Projects within a group that are connected to SharePoint inherit the group behavior.
Setting up permissions
Because SharePoint has a different permissions model than Jive, you need to understand the permissions of Jive places to set up SharePoint-side permission groups correctly.
After you set up your Jive and SharePoint connection according to the permissions recommendations described here, be careful about making changes made to permissions outside the automatic provisioning of the system. You should also block regular users from being able to modify the shared permissions of files within Jive-associated document libraries.
When you connect SharePoint to Jive, you're connecting a site collection to a place. Jive has three types of places that can be linked to a SharePoint site: social groups, spaces, and projects. Groups have a different permissions model from spaces and projects.
Restricting Jive places to specific site collections
When you configure the SharePoint add-on, the best practice is to identify one or more site collections that users can choose from when creating a Jive group, space, or project. If you identify more than one, place creators can select from a drop-down list.
If you do not specify the site collections, users are required to specify the URL of a site collection, and there are no restrictions on where the SharePoint content is stored. For most administrators, security considerations will dictate the need to place content in specific site collections.
- Jive space and project permissions Access to Jive spaces and projects is governed by associating them with a Jive user group which defines permissions for groups of users.
- Jive group permissions Jive social groups do not exist in a hierarchy or inherit permissions from anywhere else in the community.
- Implications of groups for SharePoint permissions When a restricted (Members Only, Private, or Private Unlisted) group is created, users have rights to the content on the SharePoint side according to their Jive-side group membership.
Viewing site permissions
To view specific site permissions:
- Enter the site with a site administrator user.
- At the top right corner, click Settings > Site Settings.
- Click Site Permissions.