Skip to main content
Nederlands

ICT & Technology Working Group (Suite)

Daan Roelvink
Updated
This translation was generated by artificial intelligence and may contain mistakes.

The ICT & Technology working group is responsible for implementing the technical integrations on the intranet environments. In the first phase, the technical actions focus on setting up the intranet environments (production and acceptance). Subsequently, the environment is configured with external integrations.

 

✍️ Configuring email notifications

Various emails are sent from the intranet for notifications of activities on the platform, group invitations, etc. We use SendGrid for this (see attachment at the bottom of the page for a more detailed explanation). Embrace configures this for the intranet environment so that email notifications can be sent and received. The email notifications are sent with sender: noreply-[customername]@mail.embracecloud.nl.
 

 

✍️To do - Configure authentication integration

Besides our own authentication method Embrace Forms, we can also have authentication done via 3rd party Identity Providers. Perform the configuration of the desired identity provider:

 

✍️To do - Create Embrace account

When authentication of the intranet environment is via a 3rd party Identity Provider, an account for Embrace must be created in the AD. This can be one general account (Embrace Support) (if necessary multiple personal accounts). This is needed so that Embrace can log in via the linked authentication method and provide support on the environment during implementation and afterwards. 

Requirements for the account:

  • The account must contain first name, last name and email address. This applies to all accounts on the intranet. For Embrace, an account Embrace (first name), Support (last name), embracesupport@domainname.nl would suffice.
  • The password must be strong and comply with our information security policy: 
    at least 20 characters, consisting of uppercase letters, lowercase letters, numbers and symbols. Have the password generated by a password tool.

 

✍️To do - Configure profile synchronization
 

It is possible to synchronize profiles with an external source (Entra ID or ADFS), think of profile fields and archiving employees who have left. Perform the configuration of the desired source:
 

 

✍️To do - Configure MFA

If desired, multi-factor authentication (MFA) can be configured for the intranet environment. It is possible to enforce multi-factor authentication for the intranet. This can be configured in the intranet or via the linked identity provider.

 

✍️To do - Configure external integrations

 

✍️To do - Technical actions at go-live

Often technical actions are needed on the day of go-live of the new intranet, or in the days before. 

  • Automatically start intranet
    It can be set that the URL of the intranet should be the default website opened when an intranet browser (for example: Google Chrome, Safari, Microsoft Edge) is started. Additionally, it can also be set that an intranet browser (with the intranet as default website) is started when the computer starts up.
  • Give all employees access to the intranet
    If during implementation access to the intranet was limited to a certain group (project members, ambassadors, etc.), it must be ensured that all employees of the organisation have access to the intranet on the day of go-live.
  • Be on stand-by at go-live
    It is useful if someone from the ICT & Technology working group is on stand-by for technical questions and/or issues on the day of launch. Embrace staff are also on stand-by (consultant and Delivery staff), so quick action can be taken in case of any technical issues.