Correct private app limitation on Community Cloud (#1296)

* Correct private app limitation on Community Cloud

* Clarification

* Copilot suggestion

Author: sfc-gh-dmatthews

content/develop/api-reference/user/user.md

@@ -8,8 +8,6 @@ description: st.user returns information about the logged-in user of private app
 
 ### Community Cloud
 
-On Community Cloud, if your app is not configured for authentication, `st.user` will have a single attribute: `email`. If a user is logged in and a member of your app's workspace, this will return the user's email. For all other cases, it returns `None`.
-
-On Community Cloud, if your app is configured for authentication (`[auth]` exists in your app's secrets), `st.user` will behave the same as a locally running app. Remember to update your identity provider's configuration and your app's secrets to allow your new domain. A list of [IP addresses](/deploy/streamlit-community-cloud/status#ip-addresses) used by Community Cloud is available if needed. An authentication-configured app counts as your one, allowed private app.
+Starting from Streamlit version 1.42.0, you can't use `st.user` to retrieve a user's Community Cloud account email. To access user information, you must set up an identity provider and configure authentication (`[auth]`) in your app's secrets. Remember to update your identity provider's configuration and your app's secrets to allow your new domain. A list of [IP addresses](/deploy/streamlit-community-cloud/status#ip-addresses) used by Community Cloud is available if needed. An authentication-configured app counts as your single allowed private app.
 
 <Autofunction function="streamlit.user.to_dict" oldName="streamlit.experimental_user.to_dict" />