Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determine (default) type of user using Element #525

Open
Half-Shot opened this issue Jul 26, 2022 · 1 comment
Open

Determine (default) type of user using Element #525

Half-Shot opened this issue Jul 26, 2022 · 1 comment
Labels
A-Config A-Onboarding The users first experience of Element, whether that be first impressions or first tasks. O-Occasional Affects or can be seen by some users regularly or most users rarely T-Feature Request to add a new feature which does not exist right now X-Needs-Investigation Z-NewUserJourney

Comments

@Half-Shot
Copy link
Member

Follow-up on #252

I won't restate all the context in the previous issue, but we'd like to determine the default type of user (personal, workplace, community) that a homeserver is likely to host. EMS for instance is aware of the type of user based upon the product they have purchased (Element One, Element Home, Element Cloud are all personal products, Element Enterprise Cloud is workplace, and special cased homeservers like mozilla.org / kde.org are community).

We'd like to record this information in a way that all clients can access so they can show the ideal flow for the user. Note that this shouldn't be the only available flow, but I'd expect the design to heavily imply to new users that they should follow it (with the option to say "I know what I am doing").

@clokep already mentioned that we should ideally avoid configuring this in the homeserver itself and I am minded to agree.

The solution I'd prefer is using the client .well-known file to indicate to all clients, not just the user's hosted Element instance, that the user is of a given type. This could be a field such as io.element.user-type-hint which simple is one of three enums personal, community and workplace.

@Half-Shot Half-Shot added Z-NewUserJourney T-Feature Request to add a new feature which does not exist right now labels Jul 26, 2022
@karlabbott karlabbott added the O-Occasional Affects or can be seen by some users regularly or most users rarely label Sep 7, 2022
@karlabbott
Copy link
Contributor

I've labeled this occasional as this would pretty much be a one-time setup thing.

@karlabbott karlabbott added A-Config A-Onboarding The users first experience of Element, whether that be first impressions or first tasks. X-Needs-Investigation labels Sep 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Config A-Onboarding The users first experience of Element, whether that be first impressions or first tasks. O-Occasional Affects or can be seen by some users regularly or most users rarely T-Feature Request to add a new feature which does not exist right now X-Needs-Investigation Z-NewUserJourney
Projects
None yet
Development

No branches or pull requests

2 participants