Versions Compared

Version Old Version 7 New Version 8
Changes made by

James Seabrook

James Seabrook

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Entity

Purpose

UI

Information

Example

Users

User

Yes

Capture information about the users and store it in the Identities database

Create a user

Applications

Applications which exists

No

List of applications

eg. SEKO 360

UserApplications

Applications a user can see

No

A UserApplication record will be created on save of the User as it is for White Glove only

Janet uses White Glove

UserIdentities

What a user represents in the application

NoYes

A user identity and user role are linked in this UI. A default identity will be created when a user is created. Only In most cases only one identity is required per user although each identity can have different user roles. In some cases more than one identity will be required, for example when somebody wishes to log in as a client in order to check the data and functionality.

Default identity against a user.

UserRoles

User specific roles which can be associated with an identity

Yes

The few roles required will be created programmatically. The link from the Identity and the Role must be done through the UI.

Role 1: “Admin” type role to maintain users within White Glove, partner SEKO Farnborough. Role 2: “User” type role to process bookings

UserRolePermissions

Functional permissions

No

Permissions granted to specific roles

Programmatically created in the first instance

UserIdentityScopes

Row level security

Yes

In White Glove, scopes for the application translate as different types of row level security. If there is a need for different identities to see different data, this is implemented here.

Identities are given permission to see specific data and this has to be controlled by SEKO Farnborough.

...

User

Identity

Role

Scope

Explanation

Lucy

Internal User

“User” + “Admin”

  • Client = “*”

  • Supplier = “*”

  • Log into Smart Hub

    • See all client information

    • See all supplier information Dropdown to select client data

    • Dropdown to select supplier data

  • Add new users in Smart Hub

Lucy

Client

“Client”

Client = ”ROOM””*”

  • Log into Client Portal

    • See all ROOM client info onlyDropdown to select client

Kim

Internal User

“User”

Client = “ROOM”

  • Log into Smart Hub

    • See only “ROOM” data

Jack

Client

“Client”

Client = “ROOM”

  • Log into Client Portal

    • See only “ROOM” data

Simon

Client

“Client”

Client = “Pharma”

  • Log into Client Portal

    • See only “Pharma” data

UI Requirements

  • User Maintenance - general user information

    • Create User Identities (pass in user and identity alias and it will create the identity alone if the user already exists, otherwise it will create the user and the identity).

  • Role allocation against a user identity

  • Scope allocation against a user identity

  • Identity Selection for a given user when they log on (eg. drop-down of identity if there is more than one). The selection becomes the default until a new selection is made.

List of Users

User can be maintained in the menu option “Maintenance” which will show a list of users. This list of users contains information like

  • User ID

  • User Credentials

  • Contact Details

  • User Type

  • User Associations

    Clients and Suppliers associated with the internal user

    Identities

    • Internal user, possibly also client and supplier for specific users

    • Client for a client user

    • Supplier for a supplier user

    Advice

  • User roles for each identity

    • Client

    • Supplier

User Maintenance

Users can be

...