Versions Compared

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. White Glove, 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(and SEKO 360 WMS?)

Janet uses White Glove

UserIdentities

What a user represents in the application

Yes

A user identity and user role are linked in this UI. A default identity will be created when a user is created. 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 only

  • Role 3: Client type role for client portal

  • Role 4: Supplier type role for supplier portal

UserRolePermissions

Functional permissions

No

Permissions granted to specific roles

Programmatically created in the first instance. Allow users to access certain areas of the application based on the user role type allocated to the user.

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

    • Dropdown to select client data

    • Dropdown to select supplier data

  • Add new users in Smart Hub

Lucy

Client

“Client”

Client = ”*”

  • Log into Client Portal

    • Dropdown to select client

Kim

Internal User

“User”

Client = “ROOM”

  • Log into Smart Hub

    • See only “ROOM” data, no dropdown

Jack

Client

“Client”

Client = “ROOM”

  • Log into Client Portal

    • See only “ROOM” data, no dropdown

Simon

Client

“Client”

Client = “Pharma”

  • Log into Client Portal

    • See only “Pharma” data, no dropdown

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.

...

User Maintenance

Users can be

  • maintained, deleted, cloned and added

  • made active or inactive at any time

  • have clients or suppliers associated with it

...