As a field admin, you can read a case and view the status in the Service Cloud Admin Console. By default, the Service Cloud home page displays a list of new or open cases requiring your attention. You can also search for existing cases.
On the Service Cloud home page, click a case number.
When you open a case, you will see three main sections:
- Metadata Panel (Case Detail) 
- Summary Panel 
- Detail/Feed Panels 
View Metadata Panel
The Metadata Panel allows you to view and change details on a case.
The User's Name and User's Email fields  list the name and email of the user who submitted the case. The Case CC field  will display anyone copied on the case. To add someone, enter the user’s email address in the field. Separate multiple email addresses with commas. The Case Owner field  is the user currently assigned the case. To change the case owner, use the Transfer To drop-down menu. The Date/Time Opened field  shows the date and time the case was opened.
To save any changes made to the case, click the Save Case Details button .
Note: If you are replying to a user and click the Save Case Details button, it will refresh the page and you will lose your post.
View Status and Case Origin
The Status field  of your ticket may be New, Open, Pending, On-hold, or Solved.
- New means the case is new and needs a reply.
- Open means the case is actively being worked on. A case can remain open for as long as necessary.
- Pending is a status used by the Canvas Support Team if they are waiting for the end user to provide additional information that will help them resolve the issue. A case can remain in pending status for as long as necessary.
- On-hold is a status used by the Canvas Support Team if the case is being addressed by another department. On-hold cases should have a corresponding Jira assigned to it.
- Solved means the case has been resolved.
To change the status, select a status from the drop-down menu and click the Save Case Details button.
The Case Origin field  should be populated; if not, choosing a case origin from the following list is optional:
- In Person
- Mobile App
- Online Submission
View Canvas Component Fields
Canvas Component fields describes which area in Canvas is involved with a case and what is occurring in that area.
- The Canvas Component Section field  describes whether the Service Cloud case relates to an entire account, a specific course, a Canvas user, an LTI or integration, or a non-Canvas issue.
- The Canvas Component Affected field  describes the feature in Canvas where the bug or issue comes from.
- The Canvas Component Action field  describes the action that led to the case creation.
- The Canvas Component Issue field  describes the purpose behind the case creation.
To learn more about options available for the Canvas Components fields, view the Canvas Components PDF.
Note: If there are secondary or tertiary level items, please select those items within that feature. If there are not, please select the main feature.
View Subject, Description, and JIRA Issue Number
The Subject field  shows what the end-user typed in the subject line. The Description field  shows what the end-user typed in the case.
The JIRA Issue Number field  is for Canvas support agents to fill in when a given case is associated with a ticket in our engineering ticketing system. If a cloud case is associated with a Canvas engineering ticket, the JIRA number will be shown here.
View User ID, URL, and Become User URL
The User ID field  lists the Canvas ID for the ticket submitter. This number should not be confused with an SIS ID.
The URL field  shows where the user was when the online submission ticket was created. Encourage your end users to click the Help link from the page in Canvas where they are experiencing the problem.
The Become User URL field  shows the page where the user submitted the ticket. This URL also allows you to see what the end user sees in Canvas.
Note: These fields will either be populated or not when the case is created. If they are not populated, you do not need to fill the fields out.
View HTTP Environment and Stacktrace
The User Agent String displayed in the HTTP Environment field  indicates the end user's operating system, browser version, and IP address where it was submitted. To interpret this string, visit the user agent string website and paste the text in the window for analysis.
The Stacktrace field  contains the engineering error message. This field will be filled out if the ticket was submitted from a Page Error report. This message is usually only decipherable by the engineer who wrote the code but may contain some information that will lead you on the right path toward resolution.
Note: These fields will either be populated or not when the case is created. If they are not populated, you do not need to fill them out.
View Summary Panel
The Summary Panel gives you a quick look at some of the information regarding the case, including the case's priority level. The following options are available for priority level:
- Low: Issues that aren’t time sensitive.
- Normal: Run-of-the-mill issues, to be handled in order received.
- High: Impacts more than one user; is fairly time sensitive.
- Urgent: Impacts full departments or institution; extremely time sensitve.
View Feed Panel
To access the Feed panel, click the Feed button . At the top of the Feed View, there are options to share a post, escalate a case, attach a file, add a CC, or merge cases . The lower part of the feed includes comments, posts about status changes, and posts about other metadata changes .
Note: Cases sometimes will have conversations that have already happened between the end user and Local Support Staff from their institution. If this is the case, the exchange will be scrollable with the newest replies at the top. It’s best to start at the bottom and move up from there.
View Details Panel
To access the Details panel, click the Details button . The Detail panel includes the case metadata in a different format and case action buttons that are duplicated in the left-hand sidebar.
The Case Routing Number (CRN)  indicates a case's routing history. Learn more about the CRN in the Case Routing Number PDF.
The Account Name  will have the institution the user is associated with.
User Perceived Severity  is separate from the priority drop-down menu that the agent marks the ticket with. This helps track how urgent the issue is from the perspective of the end user. Users should reserve the Extreme Critical Emergency item for issues and bugs that really are critical emergencies.