For the complete documentation index, see llms.txt. This page is also available as Markdown.

InfoboardChannels

Introduction

InfoboardChannels organize InfoboardPosts and own the Entity Permissions that control channel access and administration.

The apply_allowed_departments setting additionally constrains which departments can be targeted by posts moved to or created in a channel.

The notifications_enabled setting controls whether posts, comments, and reactions in the channel can dispatch notifications. It does not affect resource visibility or seen and read tracking.

Model Definition

Alias

infoboardChannel

Move Posts Assignment Modes

  • any_of - Assigns every moved post to the supplied departments.

  • null - Removes explicit targeting when the target channel permits untargeted posts.

Relations

Key
Relation
Type
Relation Field(s)

user

Belongs to

user_id

folder

Belongs to

folder_id

icon

Belongs to

icon_id

entityPermissions

Morph many

entity_permissions.restrictable_type, entity_permissions.restrictable_id

infoboardPosts

Has many

infoboard_posts.infoboard_channel_id

Capabilities

  • Entity Permissions - Channels own direct grants; their Restricted Scope controls viewing, post creation, commenting, and administration without changing post Targetables.

  • URL Context - Channel URLs resolve to access-checked context information.

  • Translations - The title field is translatable.

List

List InfoboardChannels visible to the current authenticated User.

Definition

GET /api/infoboard/channels

Behavior

  • The channel Restricted Scope uses direct Entity Permissions with the view key and includes ownership and configured extended department access.

Example Request

Example Response

Show

Show one visible InfoboardChannel.

Definition

GET /api/infoboard/channels/{infoboardChannel}

Route Parameters

Parameter
Type
Description

infoboardChannel

integer

InfoboardChannel ID.

Behavior

  • The same direct Entity Permissions and ownership rules as the list endpoint apply.

Example Request

Example Response

Admin: List

List InfoboardChannels available for administration.

Definition

GET /api/administration/infoboard/channels

Behavior

  • Without unrestricted channel edit or delete permission, the result contains channels owned by the authenticated user or granted through direct Entity Permissions for administration.

  • Soft-deleted channels can be included through the shared query controls.

Example Request

Example Response

Admin: Show

Show one InfoboardChannel in administration scope.

Definition

GET /api/administration/infoboard/channels/{infoboardChannel}

Route Parameters

Parameter
Type
Description

infoboardChannel

integer

InfoboardChannel ID.

Behavior

  • Access requires ownership, a direct administration grant, or unrestricted channel edit or delete permission.

Example Request

Example Response

Admin: Create

Create a new InfoboardChannel.

Definition

POST /api/administration/infoboard/channels

Request Keys

Key
Type
Default
Description

lang_id

string

system language

Language key for the translatable title.

folder_id

integer | null

null

ID of the Folder containing the channel.

icon_id*

integer

-

ID of the Icon used by the channel.

title*

string

-

Channel title.

color

string | null

null

Channel color as a client-defined string.

apply_allowed_departments

boolean

false

Whether post department targets are limited to departments the author may assign.

notifications_enabled

boolean

true

Whether posts, comments, and reactions in the channel may dispatch notifications.

sort_number

integer

end of folder

Position among channels with the same folder_id.

Keys with * are required.

Behavior

  • The authenticated user becomes the owner; a client-provided user_id is ignored.

  • New channels enable notification dispatch by default. Setting notifications_enabled to false suppresses channel post, comment, and reaction notifications.

  • Missing, invalid, or out-of-range sort_number values are normalized within the selected folder.

Example Request

Example Response

Admin: Update

Update an existing InfoboardChannel.

Definition

PUT /api/administration/infoboard/channels/{infoboardChannel}

Route Parameters

Parameter
Type
Description

infoboardChannel

integer

InfoboardChannel ID.

Request Keys

Key
Type
Description

lang_id

string

Language key for the translatable title.

folder_id

integer | null

ID of the Folder containing the channel.

icon_id

integer

ID of the Icon used by the channel.

title

string

Channel title.

color

string | null

Channel color as a client-defined string.

apply_allowed_departments

boolean

Whether post department targets are limited to departments the author may assign.

notifications_enabled

boolean

Whether posts, comments, and reactions in the channel may dispatch notifications.

sort_number

integer

Position among channels with the same folder_id.

Behavior

  • A client-provided user_id is ignored.

  • Disabling notifications_enabled suppresses future channel post, comment, and reaction notifications; it does not change existing notification records.

  • Changing folder_id or sort_number normalizes the affected folder order.

  • Changing title removes stored translations for the previous title.

Example Request

Example Response

Admin: Move Posts

Move every InfoboardPost from one channel to another channel or out of channel scope.

Definition

PUT /api/administration/infoboard/channels/{infoboardChannel}/move-posts

Route Parameters

Parameter
Type
Description

infoboardChannel

integer

Source InfoboardChannel ID.

Request Keys

Key
Type
Description

infoboard_channel_id

integer | null

Target InfoboardChannel ID; omit or send null to remove the channel assignment.

assign_mode

string | null

Selects one of the supported Move Posts Assignment Modes.

department_ids

array | null

Department IDs assigned to every moved post.

Behavior

  • The target channel must differ from the source channel, and the authenticated user must be allowed to administer both when a target is supplied.

  • The authenticated user becomes the owner of every successfully moved post. Client-provided user_id and user_ids values are ignored.

  • Providing departments defaults assign_mode to any_of. Without departments it defaults to null.

  • For no target channel or a target with apply_allowed_departments enabled, disallowed department IDs are removed. A target with that setting enabled requires a valid any_of assignment with at least one remaining department.

  • Changing the channel resets each post's seen users, read users, comments, reactions, and targeted survey votes before the supplied departments are synchronized.

  • The response data is the number of posts successfully moved; update events and their notification side effects run for each moved post.

Example Request

Example Response

Admin: Delete

Delete an existing InfoboardChannel.

Definition

DELETE /api/administration/infoboard/channels/{infoboardChannel}

Route Parameters

Parameter
Type
Description

infoboardChannel

integer

InfoboardChannel ID.

Behavior

  • The channel is soft-deleted and removed from its sort range.

  • All posts in the channel are deleted through their normal deletion lifecycle.

  • Every department setting that used this channel as default_channel_id is changed to null.

Example Request

Example Response

Last updated