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
Is your feature request related to a problem?
Currently the private tenant can only be enabled / disabled through YML configuration files. Configuring through these files is a complex and somewhat frustrating experience for admin users. In order to enhance the UX for configuring tenancy it would be nice to offer admin users a dynamic way to enable / disable the private tenant through OpenSearch Dashboards Security Plugin.
Other context notes
By default the private tenant is the default tenant for all users if not specifically configured by the admin.
Saved objects created in private tenants can not be accessed by other users.
Saved objects created in the global tenant are accessible to all users.
The global tenant can not be disabled
Users / Personas
Admin - This is a user that has access to the security plugin and can configure tenancy. They can also use tenancy like a non-admin user would.
Non-admin - These are users that do not have access to the security plugin, they can not configure tenancy but can use the feature if it is enabled and their admin has granted them appropriate permissions to do so.
What solution would you like?
NB: These are design mockups. Some copy is placeholder and not all interactions are polished.
Mockups may differ from the final launched feature.
1. Disable private tenant
Admin users can disable the private tenant if tenancy is enabled through the configure tab.
When the private tenant is disabled the default tenant for all users is set to the global tenant, however the user is able to change this to a custom tenant of their choosing.
Friction is introduced to notify the user and force them to consider their decision
Disable.Private.Tenant.mp4
2. Non-admin user notification
When the private tenant is disabled users working in a private tenant should be shown a persistent modal notifying them that the admin has disabled the private tenant
The non-admin user is prompted with a persistent modal that can not be cancelled out of.
After a set amount of time they are redirected to the global tenant
If users try to access a tenant via a url that has been disabled they will be notified that they no longer have access
When non-admin users try and switch a tenant they do not see the private tenant option
Additional Details
These UX improvements are based on work/tasks outlined in this issue and this RFC for making tenancy dynamically configurable.
The text was updated successfully, but these errors were encountered:
Context
Is your feature request related to a problem?
Currently the private tenant can only be enabled / disabled through YML configuration files. Configuring through these files is a complex and somewhat frustrating experience for admin users. In order to enhance the UX for configuring tenancy it would be nice to offer admin users a dynamic way to enable / disable the private tenant through OpenSearch Dashboards Security Plugin.
Other context notes
Users / Personas
What solution would you like?
NB: These are design mockups. Some copy is placeholder and not all interactions are polished.
Mockups may differ from the final launched feature.
1. Disable private tenant
Disable.Private.Tenant.mp4
2. Non-admin user notification
If users try to access a tenant via a url that has been disabled they will be notified that they no longer have access
When non-admin users try and switch a tenant they do not see the private tenant option
Additional Details
These UX improvements are based on work/tasks outlined in this issue and this RFC for making tenancy dynamically configurable.
The text was updated successfully, but these errors were encountered: