Article last updated on the 4th of July, 2024.
The contents of this article may be subject to change due to ongoing development of WorkPoint Automate.
Note that before using the Create Team step, a service user must be set up and certain permission consents must be granted. Please read this article for more information.
When a WorkPoint 365 site is converted to a Microsoft Teams-enabled site (a process known as 'teamification'), there is an observed issue where site collection administrators are stripped of their administrative rights. This loss of rights occurs because the site collection administrators are being automatically added to the Owners group. This issue can result in conflicts especially when there are pre-existing security rules for Office 365 groups that inadvertently override the membership of the Owners group.
Workaround: To counter the issue of administrative rights loss during the teamification of WorkPoint 365 sites, the following workarounds can be considered:
1. Manually Add Administrators: After the teamification process has been completed, manually re-add the desired users as site collection administrators to ensure they retain the necessary permissions.
2. Configure a Security Rule: Establish an Office 365 group security rule targeting the Owners group permissions and the personnel who needs access, to maintain consistent and correct permissions post-teamification.
The "Connect entity to Office 365 group" step creates Office 365 groups for entities and connects them to Microsoft Teams sites as well. This is useful e.g. for project teams who like to work in the Microsoft Teams interface as opposed to directly in WorkPoint in the browser and/or other services. Note that whatever interface is used, documents and items are all stored in the same location the WorkPoint/SharePoint libraries. This means that users can jump from working in WorkPoint to Teams and other services, but documents will always be easily accessible in the same locations as always.
A use case could be instances where a specific project team wants to use Microsoft Teams to organize and work with their project. Perhaps because they are used to the Teams interface, or for some other reason.
The following image shows a process which includes the "Connect entity to Office 365 group" step:
Step specific properties
| Parameter name | Type | Required | Description |
|---|---|---|---|
| Business module | String | Yes | Use this field to define the business module of the entity for which you want to create a team. |
| Entity | Integer | Yes |
Use this field to define the ID of the entity for which you want to create a team. |
| Is public | Boolean | Yes |
Determines if the created Office 365 group is public or private. Yes = public, No = private. |
| Description | String | No | The description of the created Office 365 group will be set to the content of this field. The description may not exceed 1024 characters in length. |
| Group alias | String | Yes |
The created Office 365 group's alias will be set to the contents of this field. The alias is used as the URL of the SharePoint site created for the group (tenant.sharepoint.com/sites/alias) as well as the primary email address for the shared mailbox associated with the group. The group alias may not exceed 64 characters in length.
|
| Group display name | String | Yes |
The displayed name of the group will be set to the contents of this field. The display name may not exceed 256 characters in length.
|
Comments
0 comments
Please sign in to leave a comment.