mirror of
https://github.com/AppFlowy-IO/AppFlowy.git
synced 2026-03-24 04:46:56 +00:00
[GH-ISSUE #7240] [FR] Hide disabled features (self-hosting) #3208
Labels
No labels
2024
2025
2026
acct mgmt
AI
automation
bug
calendar
ci
CJK
cloud
code-block
collaboration
copy-paste
database
data migration
data sync
deploy
desktop
develop
develop
documentation
duplicate
editor
editor-plugin
emoji
export
files
flutter-only
follow-up
formula
good first issue for devs
good first issue for experienced devs
grid
hacktoberfest
HACKTOBERFEST-ACCEPTED
help wanted
i18n
icons
images
importer
improvements
infra
install
integrations
IR
kanban board
login
look and joy
mentorship
mobile
mobile
needs design
new feature
new feature
non-coding
notes
notifications
onboarding
organization
P0+
permission
platform-linux
platform-mac
platform-windows
plugins
program
pull-request
Q1 25
Q1 26
Q2 24
Q2 25
Q3 24
Q3 25
Q4 24
Q4 25
react
regression
rust
rust
Rust-only
Rust-only
Rust-starter
Rust-starter
self-hosted
shortcuts
side panel
slash-menu
sync v2
table
tablet
task
tauri
templates
tests
themes
translation
v0.5.6
v0.5.8
v0.5.9
v0.6.0
v0.6.1
v0.6.4
v0.6.7
v0.6.8
v0.7.1
v0.7.4
v0.7.4
v0.7.5
v0.7.6
v0.7.7
v0.7.8
v0.8.0
v0.8.4
v0.8.5
v0.8.9
web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AppFlowy-IO/AppFlowy#3208
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
@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! 🙏🏼
@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.
@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.
@almereyda commented on GitHub (Feb 8, 2025):
Related:
@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.
@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.
@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:
Thank you.
@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_ENABLEDtofalseon your gotrue / supabase auth container will disable email accounts.github.com/supabase/auth@01ebce1bf0/README.md (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.
@maggiv8 commented on GitHub (Sep 29, 2025):
My screenshot is from the browser / web app. I set the setting
GOTRUE_EXTERNAL_EMAIL_ENABLEDtofalse, 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.).@almereyda commented on GitHub (Oct 1, 2025):
It might be, that hiding this specific login method is not supported, yet.
@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?
@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.