Skip to main content
Eptura Knowledge Center

User Security and Environments

Overview


System Administrators are responsible for managing access to Serraview. When implementing Serraview they will work with the Eptura Implementation team to determine which users require access to each module within the system. The most common user types within Serraview are:

  • Data Manager
  • Migration Manager
  • Occupancy Planner
  • Workplace Administrator

Each of these user types will be assigned one or more roles within Serraview. Each role is made up of a set of secured actions that control their access to Serraview. Refer to Corporate Real Estate Team to understand the security roles in a business context.

Manage User Security


What is a Secured Action? 

Secured actions break down how users interact with Serraview modules and features. For example, to be able to view the VBS requires a specific secured action, while to make and save changes in the VBS requires a different secured action. This granularity allows System Administrators to control everything that the users can see and do, empowering or restricting users by adding or removing the appropriate secured actions.

Within Serraview, secured actions are grouped by module/function and are distinctly named for easy understanding.

What is a Role? 

A role consists of one or more secured actions, logically grouped together to perform a particular function within Serraview. All users must be assigned at least one role to access Serraview, and a user can have one or many roles depending on their access requirements. 

While a set of default roles are provided, the secured actions associated with each role can be modified to suit organizational needs. If required, new custom roles can be created. Learn more in Manage User Roles.

What is an Environment?

Your organization will have the following environments set up:

  • UAT environment - this is where the System Administrators can test the set up of module configuration, email setup, and security roles setup. Note that any email sent out from this environment will need to be sent out manually as the automatic emails will be turned off.
  • PROD environment - this is where the end users will complete their daily activities, and emails are sent out automatically.

Learn about the release process in Release Management.

image2020-9-8_11-38-44.png

Test User

In either environment, a System Administrator can set up a test user account to check if they have set up a user account with the correct security roles and secured actions or if they want to check if an email template is set up correctly. For more details, see Add a test user account.

Audit History


Any updates to User Security or when a user's signs into Serraview, the details are recorded in the audit history: