Article last updated on the 24th of October 2019.
Microsoft Teams is a complete chat and online meetings solution. With Microsoft Teams you can host audio and/or video and perform or attend online conferences. It also lets you communicate with other members of your organization, or even people outside your organization, through an intuitive chat feature.
This provides the users with a unique intuitive interface from which all the necessary features required for team work on various projects can be accessed.
By using automatic integration between Microsoft Teams and WorkPoint through Office 365 Groups, documents created, uploaded or edited are stored in the same location, regardless of whether the user is working through the Microsoft Teams interface, or through the WorkPoint/WorkPoint Express interface.
You can read more about Microsoft Teams specifically by visiting this link:
One 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.
Additionally, Microsoft Teams is integrated with Microsoft’s online office suite Office 365. This means that it is tied together with other apps such as Word as Excel, as well as cloud storage and services such as SharePoint, PowerPoint, OneNote, Planner, Power BI and Delve. As a consequence of this, any document, presentation, and spreadsheet shared within a Team are automatically synced with a copy stored in Microsoft’s OneDrive cloud storage as well as a local SharePoint environment. This makes it easier to keep track of all of the Team’s shared documents, and to not miss any updates, both in communication and in documents.
Microsoft Teams also has the capability to connect to outside services such as GitHub, Zendesk, Evernote, and SAP SuccessFactors. It can even connect to businesses' own internal apps through an API.
Access to files, internal sites and dashboards is controlled by Office 365 Groups and SharePoint. Users can create a new Group or attach the Team to an already existing one when creating the Team.
Security-wise Teams meet all the same security standards as Office 365 and is Office 365 Tier C compliant. The service enforces two-factor authentication, single sign on through Active Directory, and encryption of data in transit and at rest.
1.1. Connecting WorkPoint to Teams
It is possible to activate integration to Microsoft Teams in WorkPoint. The integration links entities to Microsoft Teams through Office 365 Groups. On each individual business module Office 365 Groups can be activated, given the use of the one-site architecture with the one-site-pr-entity option.
Once an entity has been connected to an Office 365 Group, a Microsoft Teams site is automatically created for that entity.
When activated, WorkPoint can automatically make sure that an Office 365 Group is created for each entity, which is linked to the site collection that WorkPoint set up. It Is, however, optional whether WorkPoint should create an Office 365 Group for each entity. This means that for e.g. a Projects module it is possible for some entities to have Team/Office 365 Group integration, while others do not.
It is also possible to make the creation of the Office 365 Group happen when certain conditions are met. An example would be that the Office 365 Group should not be created until a Project reaches the “Active” stage. All these functions can be done through Action Management.
Teams Integration is set up using Action Management, thus a specific Action Management license is required. Furthermore, Teams integration is an additional feature that is not standard with WorkPoint. If your organization would like this feature, please contact WorkPoint Sales at firstname.lastname@example.org.
Connecting a WorkPoint business module entity to an Office 365 Group is primarily done through the Action Management in WorkPoint. Generally, an action is set up to establish the connection, and this action can then be triggered in various ways. It can either be triggered manually, or dynamically based on entity data. If dynamic, establishing connection can be made conditional based on data.
3.1. Action Management Configuration
Through the Action Management settings for a given module, an Action of type “Connect to Office365 Group” can be added.
The interface for setting this type of action up is shown below:
- A Service User must be set when Groupify Action is active. You can click the “here” link to go to the setup for Service User. This service user must have the SharePoint administrator role.
- The title field holds the title of the action
- The action can either be active or non-active and can be toggled using the checker.
- A column can be selected for WorkPoint to pull data from for the Group Alias. Note that only columns of type “Single line of text” are allowed.
- A column can be selected for WorkPoint to pull data from for the DisplayName. Note that only columns of type “Single line of text” are allowed.
- A column can be selected for WorkPoint to pull data from for the Description. Note that only columns of type “Single line of text” are allowed.
- A group can be set to either be Private or Public. The state is selected from the drop-down menu. Note that a state of “Yes” means that the group is Public, while a state of “No” means that the group is Private.
The fields under Dynamic called “Confidential” and “GDPR” are columns of type Yes/no-choice on the module that is currently being worked on. Using a dynamic value means that, should the value change, so does the privacy state of the group.
This action can now be set up to be executed via button in the My Tools menu of the solution, or automatically upon a specified event, such as a stage change.
4. End User Guide
In this example, we will create an action to connect Project entities to Office 365 Groups, as well as a manual trigger for the action. We will also configure a My Tools button for the trigger, so that an end user can opt to connect his/her project to an Office 365 Group by themselves.
4.1. Action Management Settings
First, we have set up an Action of type “Add Connect to Office 365 Group”:
1. We have navigated to the Action Management settings for a Projects business module.
2. We have clicked the "Add Connect to Office 365 Group" button.
3-8 Relevant columns for information matching the fields have been filled out.
9. We click the Save-button.
We can now create an action trigger for this action, e.g. a manual trigger to connect to Office 365 Groups:
- We are in the Action Management dashboard
- We click the “Add Manual Trigger” button
- We give the trigger a title
- We set the permission required for this trigger
- We select the Action we want to trigger
- We click “Add” to add the Action to the list of actions to be triggered
- We click “Save”
4.2. MyTools Configuration
After having set up the Actions and Triggers to connect the module to Office 365 Groups, we can configure a button in our My Tools panel to execute the actions:
- We are in the My Tools dashboard
- The Projects business module is selected
- In the list of buttons and button groups, the Actions group is selected
- We click “Add button” in the side menu
We configure the button as follows:
- The title of the My Tools button is typed in
- A fitting icon is chosen
- A type of Manual Trigger is chosen
- As Manual Trigger is chosen, we can choose the trigger we created earlier, called “Connect to Office 365 Group”
We end the setup by clicking “Save” in the side menu. Before we can see the changes made to the My Tools menu, we need to clear the WorkPoint 365 Browser Cache. This can be done by following these steps:
- Open the Home menu and at the bottom, click “Need help?”
- Click “Clear WorkPoint 365 Browser Cache”
In the My Tools panel for Project entities the new button to connect the project to an Office 365 group is now accessible:
Once connected to an Office 365 Group, WorkPoint automatically generates a link to the Teams Site as well as an Office 365 group ID. Both of these can be seen in the Projects list, as shown in the image below:
By clicking “Go to Teams”, the user can access the Teams Site for the project.
Inside the project’s site, it is possible to add the link to go to the Teams site for the project to the Entity details panel as shown in this image (link marked in green):
Additions have been made to WorkPoint’s security rules. It is now possible to make security rules which target Office 365 Group membership specifically. This means that “owner” and “member” of the Office 365 Group can be fetched from attributes of the entity in WorkPoint (e.g. Project Manager or Project Team). This has been made possible through the addition of new scopes on new security rules on relevant modules where the Office 365 Group feature is activated (shown below).
Once Office 365 Group has been chosen, the administrator can choose which group membership to target. Group memberships can be the standard Office 365 group memberships, e.g. “owner” or “Member”, but can also be customized groups. An example is shown in the image below:
Please note, that when selecting "Owners" for Group permission, only required fields are available in "Field name".
Should an entity not be linked with a group, the security rules of groups are ignored.