forked from RocketChat/Rocket.Chat
-
Notifications
You must be signed in to change notification settings - Fork 1
Web client survey
mr_kite edited this page Dec 7, 2018
·
27 revisions
This wiki describes features in the web client that we would like to disable, in a Viasat Connect
version of the app. It also poses some questions where it is unclear. Some features can be disabled through permissions, and others will require dev work in order to remove them. This is meant as a starting point to help organize the work on the web client.
This wiki does not address Viasat Connect
look and feel issues, i.e. colors, assets, etc.....
This issue upstream begins a discussion for configurability in the User Preferences
options.
- Only offer SSO option for login. Does this pose a problem for the initial admin user?
- Current configurability: email/password login fields can be disabled at Admin>Accounts>Show Default Login Form.
- We need new copy for the home page.
- Current configurability: home page text editable at Admin>Layout>Content.
- Disable the ability to create public channels as well as the
Read Only
andBroadcast
channel properties. - Current configurability: public channel creation can be disabled by role at Admin>Permissions. The setting toggle still shows up for the user but is greyed out with "Private Channel".
Read Only
andBroadcast
are not currently configurable.
- The directory button allows the user to search all
channels
and allusers
. We may want to disable or limit the search scope to users with whom there are already open DMs, and channels that you own or are a part. Is there such thing as afriends
search, orinvite friends
in the web client???
- The normal search does a global user search. Do we want to limit that to only
friends
with whom we are already chatting?
- Make all options configurable by an admin. Upstream issue here
- Only
Profile Picture
andDelete my account
should be configurable by the user because SSO will be solely responsible for profile information. None of the rest should be enabled, but they should be visible. Do we want a link to SSO from here???
- Do we want to allow users to configure 2FA?
- What the heck is this?? We should remove it entirely.
- What the heck is this for??