> 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/resources/portfolio_notifications.md).

# Portfolio Notifications

Used by the Portfolio LTI tool to emit a Canvas notification for a recipient user. This does not persist a domain record; it dispatches the shared "Portfolio Event" notification through the standard pipeline (respecting the recipient's /profile/communication preferences and daily/weekly digest for the "Portfolio" category), carrying the per-event copy in the message `data` hash -- the same approach other data-only notifications (e.g. 2fa) use.

The notification is recipient-scoped, not course-scoped. Authorization is a shared-context check: the caller may only notify someone Canvas already considers messageable from them (they share a course/group) -- the same rule Conversations uses to decide who you can message.

## [Create a portfolio notification](#method.portfolio_notifications.create) <a href="#method.portfolio_notifications.create" id="method.portfolio_notifications.create"></a>

[PortfolioNotificationsController#create](https://github.com/instructure/canvas-lms/blob/master/app/controllers/portfolio_notifications_controller.rb)

#### `POST /api/v1/users/:user_id/portfolio_notifications`

**Scope:** `url:POST|/api/v1/users/:user_id/portfolio_notifications`

***

This documentation is generated directly from the Canvas LMS source code, available [on Github](https://github.com/instructure/canvas-lms).


---

# 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://developerdocs.instructure.com/services/canvas/resources/portfolio_notifications.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.