> 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_sis.md). # SIS Data - manage ## What it Does ### Account Navigation Determines visibility of SIS Import link in Account Navigation. Allows user to view the previous SIS import dates, errors, and imported items. ### Course Settings Allows user to edit the course SIS ID. ### People (Account) Allows user to view and edit the SIS ID and Integration ID in a user’s Login Details. ### People (Course) Allows user to edit the course SIS ID. ### Subaccount Settings Allows user to view and insert data in the SIS ID field. ## Additional Considerations ### Course Settings To edit course settings, Courses - manage must be enabled. ### People (Account) To view or edit a user’s SIS ID or Integration ID, Users - view list and Users - manage login details must also both be enabled. ### People (Course) If this permission is enabled, users do not need the SIS Data - read permission enabled. The account permission overrides the course permission. To disallow users from managing SIS IDs at the course level, SIS Data - manage and SIS Data - read must both be disabled. To add or remove users to a course, the appropriate Users permission must be enabled (e.g. Users - Teachers). ### SIS Import To import SIS data, SIS Data - import must also be enabled. ### Subaccounts Not available at the subaccount level. --- # 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_sis.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.