# Per-user access (OIDC)

**Summary:** Call the info-with-content-access endpoint with a logged-in member's OIDC access token to find out which Content Channels the member can access.

- Space: [Developers](https://www.subrite.no/developers)
- Source: https://www.subrite.no/developers/content-channels-api
- Updated: 2026-09-23
- Markdown index: https://www.subrite.no/developers/llms.txt

To ask the API which Content Channels a member should have access to, you need an [OIDC integration with Subrite](https://www.subrite.no/developers/oauth-integration?md=true). The OIDC flow provides an access token that you submit in the API requests, so they run on behalf of the logged-in user.

<a id="step-1-get-the-member-s-content-channels"></a>
## Step 1: Get the member's Content Channels

Use the `info-with-content-access` API call to get information about the logged-in member, including which Content Channels the member should have access to.

- **Method:** `GET`
- **Route:** `{baseUrl}/api/v1/members/profile/info-with-content-access`
- **Authorization:** Bearer token (the user's JWT access token)

The response includes the content channels:

```javascript
{
  ...
  "contentChannels": [
    {
      "id": 1,
      "name": "…",
      "description": "…",
      ...
    }
  ]
  ...
}
```

More details on this API are in the API reference: [Get logged in member info with content access](https://docs.subrite.no/api-reference#tag/member-profile/get/api/v1/members/profile/info-with-content-access).