> For the complete documentation index, see [llms.txt](https://developerdocs.instructure.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developerdocs.instructure.com/services/canvas/permissions/details/file.permissions_manage_account_settings.md). # Account-level settings - manage ## What it Does ### Account Settings Allows user to view and manage the Settings and Notifications tabs in Account Settings. ### Subaccounts Allows user to view and manage subaccounts for the account. ### Terms Allows user to view and manage terms for the account. ### Theme Editor Allows user to access the Theme Editor. ## Additional Considerations ### Announcements The Announcements tab is always visible to admins; however, to manage announcements, Global Announcements - add / edit / delete must also be enabled. ### Feature Options (Account Settings) To manage the Feature Options tab, Feature Options - enable disable - must also be enabled. ### Reports (Account Settings) To view the Reports tab, Reports - manage must also be enabled. ### Subaccount Navigation (Account Settings) Not all settings options are available at the subaccount level, including the Notifications tab. --- # 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://developerdocs.instructure.com/services/canvas/permissions/details/file.permissions_manage_account_settings.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.