> For the complete documentation index, see [llms.txt](https://docs.linuxfoundation.org/lfx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.linuxfoundation.org/lfx/organization-dashboard/users-faqs.md). # Users FAQs #### **Can admins update key contacts in Org Dash?** Yes, admins can update key contacts in Org Dash. #### **How do admins update board/committee members?** Admins cannot add new committee users in Org Dash; this is done in PCC (Project Control Center). However, admins can reassign committee roles in Org Dash. #### **How does the information propagate from Org Dash to PCC when a committee role is changed?** The change made in Org Dashboard is automatically reflected in PCC, including updating the mailing list and adding the new member to meetings (next meeting). #### **How are committee changes currently handled (e.g., mailing list, meetings)?** Committee changes are currently handled by updating the mailing list and adding the new member to meetings (next meeting) in PCC. #### **How often are committee changes reflected in PCC?** Committee changes made in Org Dash are automatically reflected in PCC in real-time. #### **Why is real-time or daily notification of committee changes important?** Real-time or daily notification of committee changes is important for day-to-day business and to ensure that PMOs are informed of changes in a timely manner. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.linuxfoundation.org/lfx/organization-dashboard/users-faqs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.