[GH-ISSUE #7240] [FR] Hide disabled features (self-hosting) #3208

Closed
opened 2026-03-23 21:28:25 +00:00 by mirror · 12 comments
Owner

Originally created by @philiprenich on GitHub (Jan 19, 2025).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7240

Description

It would be nice to hide elements on the app that cannot work, due to how the backend is configured. Register and log in via socials (Google, Apple, Github, etc) should not be shown if the backend does not support them. Self-hosters need to provide API keys for all of these services. I'm not going to bother going to every one and set up an application with them, nor do I want to use them or offer them to others who use my instance. To simplify the onboarding, I would like to hide those options when they don't have configuration values.

Similarly, I am not going to offer LLMs on my instance. I don't have accounts or use them, so it would be a better user experience to not have the various "Ask AI" or other "AI" options around the app. When used, they throw errors which is going to confuse non-technical users who just want to be better organised.

Impact

Users and owners of self-hosted instances who don't need (or have) alternative sign-on options. And those who don't want to use LLMs.

Additional Context

Forgejo (open source git & devops software) has a similar thing - registration/sign up options are configurable. It makes for a less confusing onboarding experience and less error prone ongoing usage.

Originally created by @philiprenich on GitHub (Jan 19, 2025). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7240 ### Description It would be nice to hide elements on the app that cannot work, due to how the backend is configured. Register and log in via socials (Google, Apple, Github, etc) should not be shown if the backend does not support them. Self-hosters need to provide API keys for all of these services. I'm not going to bother going to every one and set up an application with them, nor do I want to use them or offer them to others who use my instance. To simplify the onboarding, I would like to hide those options when they don't have configuration values. Similarly, I am not going to offer LLMs on my instance. I don't have accounts or use them, so it would be a better user experience to not have the various "Ask AI" or other "AI" options around the app. When used, they throw errors which is going to confuse non-technical users who just want to be better organised. ### Impact Users and owners of self-hosted instances who don't need (or have) alternative sign-on options. And those who don't want to use LLMs. ### Additional Context Forgejo (open source git & devops software) has a similar thing - registration/sign up options are configurable. It makes for a less confusing onboarding experience and less error prone ongoing usage.
Author
Owner

@philiprenich commented on GitHub (Jan 19, 2025):

ps - wasn't sure if this belonged here or in the Cloud repository. Let me know if I should copy/paste it there instead! 🙏🏼

<!-- gh-comment-id:2600778579 --> @philiprenich commented on GitHub (Jan 19, 2025): ps - wasn't sure if this belonged here or in the Cloud repository. Let me know if I should copy/paste it there instead! 🙏🏼
Author
Owner

@khorshuheng commented on GitHub (Jan 19, 2025):

@philiprenich No worries, this is the correct place to raise the issue. There are some issues which request for the exact same features, so we might consolidate them in the future.

<!-- gh-comment-id:2600886067 --> @khorshuheng commented on GitHub (Jan 19, 2025): @philiprenich No worries, this is the correct place to raise the issue. There are some issues which request for the exact same features, so we might consolidate them in the future.
Author
Owner

@philiprenich commented on GitHub (Jan 19, 2025):

Sounds good! And sorry, I tried to search for relevant issues before posting, but must have missed them.

<!-- gh-comment-id:2600989645 --> @philiprenich commented on GitHub (Jan 19, 2025): Sounds good! And sorry, I tried to search for relevant issues before posting, but must have missed them.
Author
Owner

@almereyda commented on GitHub (Feb 8, 2025):

Related:

  • #6751
  • #6834
    • in which @nitn3lav had offered to try to implement this, if they only had gotten a response
<!-- gh-comment-id:2645865115 --> @almereyda commented on GitHub (Feb 8, 2025): Related: - #6751 - #6834 - in which @nitn3lav had offered to try to implement this, if they only had gotten a response
Author
Owner

@maggiv8 commented on GitHub (Aug 19, 2025):

Hi there,

I am also trying to hide these options (i.e. hide not-configured AI options and not-configured/support sign-in options like Google, etc.). Is this possible somehow and if so how?

Thank you.

<!-- gh-comment-id:3199112095 --> @maggiv8 commented on GitHub (Aug 19, 2025): Hi there, I am also trying to hide these options (i.e. hide not-configured AI options and not-configured/support sign-in options like Google, etc.). Is this possible somehow and if so how? Thank you.
Author
Owner

@almereyda commented on GitHub (Sep 27, 2025):

Hiding unconfigured identities is now available on AppFlowy Web.

It remains unavailable on the cross-platform native app.

<!-- gh-comment-id:3342070975 --> @almereyda commented on GitHub (Sep 27, 2025): Hiding unconfigured identities is now available on AppFlowy Web. - https://github.com/AppFlowy-IO/AppFlowy-Web/issues/105 It remains unavailable on the cross-platform native app. - https://github.com/AppFlowy-IO/AppFlowy/issues/5534
Author
Owner

@maggiv8 commented on GitHub (Sep 27, 2025):

@almereyda: it seems the latest Appflowy-Cloud version supports this request. However, going through all of these message, could you please explain how exactly I can hide the following entries:

Image

Thank you.

<!-- gh-comment-id:3342092063 --> @maggiv8 commented on GitHub (Sep 27, 2025): @almereyda: it seems the latest Appflowy-Cloud version supports this request. However, going through all of these message, could you please explain how exactly I can hide the following entries: <img width="515" height="467" alt="Image" src="https://github.com/user-attachments/assets/9849cbf5-b8ce-41e2-ab48-f04f00e080ec" /> Thank you.
Author
Owner

@almereyda commented on GitHub (Sep 28, 2025):

It depends on what we are looking at here. If this is showing the native Desktop or Mobile Flutter app, you are probably best to follow and subscribe to

It appears setting the GOTRUE_EXTERNAL_EMAIL_ENABLED to false on your gotrue / supabase auth container will disable email accounts.

It remains to be evaluated wether it is supported anywhere across the AppFlowy apps to hide it, when not reported as present by the public gotrue introspection API.

<!-- gh-comment-id:3343364109 --> @almereyda commented on GitHub (Sep 28, 2025): It depends on what we are looking at here. If this is showing the native Desktop or Mobile Flutter app, you are probably best to follow and subscribe to - https://github.com/AppFlowy-IO/AppFlowy/issues/5534 It appears setting the `GOTRUE_EXTERNAL_EMAIL_ENABLED` to `false` on your gotrue / supabase auth container will disable email accounts. - https://github.com/supabase/auth/blob/01ebce1bf01b563105d653ff168a16e72c12d481/README.md?plain=1#L196 It remains to be evaluated wether it is supported anywhere across the AppFlowy apps to hide it, when not reported as present by the public gotrue introspection API.
Author
Owner

@maggiv8 commented on GitHub (Sep 29, 2025):

My screenshot is from the browser / web app. I set the setting GOTRUE_EXTERNAL_EMAIL_ENABLED to false, yet as you can see in the screenshot it still provides alternative sign-in options (e.g. I want to restrict it to email only based on admin setup, no Google, 'More Options' link, etc.).

<!-- gh-comment-id:3349090291 --> @maggiv8 commented on GitHub (Sep 29, 2025): My screenshot is from the browser / web app. I set the setting `GOTRUE_EXTERNAL_EMAIL_ENABLED` to `false`, yet as you can see in the screenshot it still provides alternative sign-in options (e.g. I want to restrict it to email only based on admin setup, no Google, 'More Options' link, etc.).
Author
Owner

@almereyda commented on GitHub (Oct 1, 2025):

It might be, that hiding this specific login method is not supported, yet.

<!-- gh-comment-id:3356526266 --> @almereyda commented on GitHub (Oct 1, 2025): It might be, that hiding this specific login method is not supported, yet.
Author
Owner

@maggiv8 commented on GitHub (Oct 1, 2025):

Now I am co fused. Isn't this threat about exactly this topic: being able to hide these kind of login methods (and LLM models) on a granular basis?
If this is not yet supported on a granular level, shouldn't we leave this threat open?

<!-- gh-comment-id:3357958011 --> @maggiv8 commented on GitHub (Oct 1, 2025): Now I am co fused. Isn't this threat about exactly this topic: being able to hide these kind of login methods (and LLM models) on a granular basis? If this is not yet supported on a granular level, shouldn't we leave this threat open?
Author
Owner

@almereyda commented on GitHub (Oct 8, 2025):

I think it was just overlooked. I've added a note to https://github.com/AppFlowy-IO/AppFlowy/issues/5534#issuecomment-3381367883, which remains open as of now.

<!-- gh-comment-id:3381368964 --> @almereyda commented on GitHub (Oct 8, 2025): I think it was just overlooked. I've added a note to https://github.com/AppFlowy-IO/AppFlowy/issues/5534#issuecomment-3381367883, which remains open as of now.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AppFlowy-IO/AppFlowy#3208
No description provided.