Staff Data
A spreadsheet of profile data fields is needed to clarify:
- where staff data will be coming from and when
- how it will be managed after launch
To be considered:
- Fields required for person profiles (to be confirmed in research phase)
- Databases where the data currently resides (to identify if migration is required)
- Which fields staff are allowed to update themselves (e.g. profile picture)
- In the case of fields staff should not update, we must provide contact details for change requests
- Which fields require a one-off import or ongoing integration
Active Directory
A review of AD is required to make sure it can populate intranet staff profiles. A key success factor for your intranet is ensuring users fill out as little as possible within their profiles. The more data we can take from AD the better. The review may highlight issues with existing AD data.
To be considered:
- Is AD staff data complete?
Staff data is often kept in other systems, e.g., HR databases. Any user-relevant data must be in AD to sync with user profile fields
- Is AD organisational data clean and consistent?
We recommend all organisational data (teams, departments, services, sites etc.) should come from AD, rather than users updating their profiles themselves. Requirements for this to happen:
- AD organisational fields must be complete for each user
- AD organisational data must be standardised (e.g. we cannot sync “Comms.” and “Communications” within the intranet’s organisational model)
See Active Directory and User Authentication - Allowing access to your site for further information