You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating a new project for every new user on login will cause unnecessary bloat on any database that is used.
This would be easier for admin/management of the litmus UI if we can default a user to a known project (e.g. the Admin project) with the role of viewer. However if this option is exposed as an optional Environment variable and the application creates that project on startup then we can assign all new users into a generalized location
Current Management of Users Workflow
WITHOUT DEX
Start application from Helm chart
Admin user creates a user
User signs in and gets a new project solely for them
Admin invites user to X project with X role
User should then delete personal project (but most likely won't because it's not forced)
WITH DEX
Start application from Helm chart
User signs in with Single Sign On and gets a new project solely for them
Admin invites user to X project with X role
User should then delete personal project (but most likely won't because it's not forced)
Desired Management of Users Workflow
WITHOUT DEX
Start application from Helm chart with an ENV var (e.g. DEFAULT_PROJECT_NAME=admin). ***
User signs in with basic authentication (username and password) and automatically gets ASSIGNED as a Viewer in the default project
WITH DEX
Start application from Helm chart with an ENV var (e.g. DEFAULT_PROJECT_NAME=admin). ***
User signs in with Single Sign On and automatically gets ASSIGNED as a Viewer in the default project
*** If Project does not already exist the application should create it
CAVEAT
If the optional ENV var is not set then the process should remain the same as it currently is as that may be the desired outcome of many project admins
The text was updated successfully, but these errors were encountered:
Description
Creating a new project for every new user on login will cause unnecessary bloat on any database that is used.
This would be easier for admin/management of the litmus UI if we can default a user to a known project (e.g. the Admin project) with the role of viewer. However if this option is exposed as an optional Environment variable and the application creates that project on startup then we can assign all new users into a generalized location
Current Management of Users Workflow
WITHOUT DEX
WITH DEX
Desired Management of Users Workflow
WITHOUT DEX
DEFAULT_PROJECT_NAME=admin
). ***WITH DEX
DEFAULT_PROJECT_NAME=admin
). ****** If Project does not already exist the application should create it
CAVEAT
If the optional ENV var is not set then the process should remain the same as it currently is as that may be the desired outcome of many project admins
The text was updated successfully, but these errors were encountered: