Canvas External Apps FAQ

Every External App must be reviewed and approved before being added to Canvas. During the review process, the app is evaluated for the type of content that is shared between the tool and Canvas. The tool is evaluated for compliance with TXST policies related to information security, FERPA compliance, accessibility compliance, cost, and legal responsibility. Form submission deadlines for Fall, Summer, and Spring semesters can be found on the form.

If you would like to request an external tool, submit a TXST Canvas External Tool (LTI) Request.

  • LTI provides a framework through which an LMS (Canvas) can send some verifiable information about a user to a third party. For LTI to work, the third party needs to provide a consumer key and shared secret that Canvas can use to generate a signature to verify the authenticity of the data sent. By default most user information is anonymized, but this can be changed when the configuration is first set up.

    External Apps add functionality to a Canvas course. For example, an instructor may want to include a study aid (flashcards, mini-quizzes, etc.) to help students better understand the concepts being taught.

    If apps do not already exist for a course, instructors can add external apps in their courses to create additional learning paths for students. External apps can be added to Modules, Course Navigation, the Rich Content Editor, and Assignments.

  • Generally speaking, you should submit a request at least one full semester previous to the app's implementation.

    • Fall semester - requests submitted by March 1
    • Summer semester - requests submitted by Feb 15
    • Spring semester - requests submitted by August 1

    NOTE: Submitting your Canvas integration request by or before the dates above does not guarantee that an external app will be approved.

  • This is a lengthy and meaningful process with many teams involved.

    The review, evaluation, and implementation process can take several weeks or months from the time of initial request.

  • The request is sent to the LMS Steering Committee.

    This committee is on the list of Committees and Councils, chaired by the Associate Provost with additional academic representation from academic colleges, as well as the ITAC LMS Product Manager, Office of the Vice President for Information Technology, and relevant technical representation from IT as needed.

  • The committee may meet as frequently as needed to conduct business, but no less than three times per year; once each fall, spring, and summer.  

  • You can check the External Apps (LTI) list, found here.

    Some may be visible in your course already, but many are hidden by default, so you'll need to find them in order to use them in your course. Most are installed in all TxState courses, but some are restricted to specific campuses, schools, or departments.

    1. Navigate to the desired course.
    2. In the course navigation menu, click Settings.
    3. On the course Settings screen, click Apps.
    4. On the Apps tab, click View App Configurations.
      On the External Apps screen, you'll see all the apps installed in your course. Apps with a lock icon to the left of their name were added by an administrator at the university, campus, school, or department level and cannot be modified or removed. Apps with the settings (gear) drop-down menu on the right were added by a teacher or equivalent role within the current course. They can be modified or removed as needed.
  • Requests can be in one of five statuses:

    • Under Review - the app is being reviewed and vetted by the committee.
    • On Hold - the app was in the process of being vetted, but has been put on hold pending more information from the vendor.
    • Authorized - the app has been authorized for use within Canvas.
    • Not Authorized - the app has NOT been authorized for use within Canvas.
    • Withdrawn - the request was withdrawn during the review/vetting process.
  • There may be many different reasons an app is not authorized for use within Canvas. Some of the reasons include (but are not limited to):

    1. The app duplicates and/or causes conflicts with an existing tool or functionality within Canvas.
    2. The app is non-compliant with Accessibility standards as required by State and Federal law.
    3. The app is non-compliant with information security standards of the university.
    4. The app does not have a dedicated funding source.