WG-545 - Getting issue details... STATUS
Background
User Maintenance implements the Indigina Core User Identities functionality which uses a secure database and is designed and implemented as follows:
/wiki/spaces/TD/pages/3385950227
The White Glove Application requires UI to a number of these entities.
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 | No | A user identity and user role are linked in this UI. A default identity will be created when a user is created. Only one identity is required per user although each identity can have different user roles. | 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. |
Example of Real User Records
Application: White Glove
Partner: SEKO Farnborough
User | Identity | Role | Scope | Explanation |
|---|---|---|---|---|
Lucy | Internal User | “User” + “Admin” |
|
|
Lucy | Client | “Client” | Client =”ROOM” |
|
Kim | Internal User | “User” | Client = “ROOM” |
|
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
Client for a client user
Supplier for a supplier user
Advice
User Maintenance
Users can be
maintained deleted, cloned and added
made active or inactive at any time
have clients or suppliers associated with it