> For the complete documentation index, see [llms.txt](https://kb.aris.college/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.aris.college/english-us/mypocket-id-internal-access-only.md).

# myPocket ID (Internal access only)

One identity for ARIS services.

myPocket ID is the single sign-on (SSO) and identity service for ARIS College. It provides a common way to identify yourself and sign in to supported ARIS services without every service needing a completely separate account and sign-in system.

Unlike myBox or myDesktop, myPocket ID isn't really a workspace or an app you'll spend much time inside. Most of the time, you'll encounter it automatically when another ARIS service needs you to sign in.

myPocket ID is an internal ARIS College service and is available only to authorized users.

### Where will I see myPocket ID?

At the moment, myPocket ID can be used to sign in to **Canvas LMS** where the myPocket ID sign-in option is provided.

When you choose to sign in with myPocket ID, you'll be taken to the ARIS identity service to authenticate. Once your identity has been verified, you'll be returned to Canvas and signed in to the account associated with your ARIS identity.

As more ARIS services support myPocket ID in the future, the same identity may be used to access them without creating another completely separate login for each service.

### What does myPocket ID do?

**Sign in to supported services**\
Use your ARIS identity to access services that have been connected to myPocket ID.

**Keep your identity consistent**\
Your identity can be recognized across supported ARIS systems rather than each service treating you as an unrelated account.

**Reduce separate sign-ins**\
When services support myPocket ID, you don't need to manage an entirely separate sign-in method for every application.

**Connect your ARIS services**\
myPocket ID acts as the identity layer between you and compatible ARIS services. The service you're opening can rely on myPocket ID to verify who you are.

### Using myPocket ID with Canvas

When Canvas asks you to choose a sign-in method, you may be given the option to continue with **myPocket ID**.

Selecting it will temporarily take you away from Canvas to complete authentication with ARIS. After a successful sign-in, myPocket ID securely confirms your identity to the connected service and sends you back to Canvas. This kind of application-to-SSO redirection is a standard SSO flow.

You generally don't need to open myPocket ID separately before visiting Canvas. Just start from Canvas and choose myPocket ID when asked.

### Access is still controlled

Having an ARIS account doesn't necessarily mean every service connected to myPocket ID is available to you.

myPocket ID handles who you are. Individual services can still determine whether your account is allowed to use them.

This means successfully signing in with myPocket ID doesn't automatically grant access to every internal ARIS service. Your account must still have the appropriate access for the service you're trying to open.

The guides in this section cover signing in with myPocket ID, using it with Canvas LMS, managing your identity, and resolving common sign-in problems.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kb.aris.college/english-us/mypocket-id-internal-access-only.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
