The White Oaks portal has six different types of users: Admin, Accounting, Field Project Manager, Operational, Vendor and Hourly Field Employee. Each user has individual rights as per the type of the user. The users are created by the admin and the admin assigns all the rights, privileges and credentials to most of the users. While the Vendors can onboard themselves. To log in to White Oaks, the user will be provided with a username and password by the admin. Once the user is logged in and the user lands on the main dashboard, there is a header and a side menu bar. The header contains the User, language, notifications and support tab.
Navigation Bar
The Navigation Bar has the White Oaks logo, Help, Support, Language, Notifications and User Settings.
User
The User tab allows to change user settings, change passwords and sign out of the portal.
Language
The user can choose the language that the user is fluent in from the given options. Currently, only English and Spanish are being supported.
Notification
It gives an insight into all the notifications being generated. A small icon on the left shows the type of notification it is: Error, Warning or Info. The top line shows the address of the site. The middle line shows the change in status of the project from one state to another. The last line shows the number of hours when the notification was generated.
Support
From the support tab, the user can take help from the team by generating a ticket.
When the ticket is being created, the following details are required Created By, Created Date, Issue Type, Severity, Status, Title, Description, Resolution and add an attachment. The user enters the Issue Type, Severity, Title, Description and adds an attachment. The greyed out fields are system generated.
There are two types of issues: Bug and Feature Requests. The Severity of the ticket has three options: Major, Low and Medium. The status will be ‘New’ as a new ticket is being generated. The description of the ticket contains the details about why the ticket is being generated. A resolution has details such as mapping to the right issue, sprint and the release it will go to in production.
Click on ‘Save’ to generate a ticket and notify the team regarding the issue.