InfoboardDepartmentSettings
Introduction
InfoboardDepartmentSettings store one settings object per Department. The current public setting selects an optional default InfoboardChannel.
Administration endpoints can upsert settings for one department or apply the same settings to several departments.
Model Definition
Alias
infoboardDepartmentSettings
Relations
Show Current
Show the InfoboardDepartmentSettings for the authenticated user's primary department.
Definition
GET /api/infoboard/department-settings/current
Behavior
The response is
nullwhen the department has no settings record.
Example Request
Example Response
Admin: List
List all InfoboardDepartmentSettings in administration scope.
Definition
GET /api/administration/infoboard/department-settings
Example Request
Example Response
Admin: Show by Department
Show InfoboardDepartmentSettings for one department.
Definition
GET /api/administration/infoboard/department-settings/{department}
Route Parameters
department
integer
Department ID.
Example Request
Example Response
Admin: Create or Update by Department
Create or update InfoboardDepartmentSettings for one department.
Definition
POST /api/administration/infoboard/department-settings/{department}
Route Parameters
department
integer
Department ID.
Request Keys
settings*
object
-
Complete Infoboard settings object for the department.
Keys with * are required.
Behavior
department_idis derived from the route anduser_idfrom the authenticated user; client-provided values are replaced.An existing record for the department is updated instead of duplicated.
Example Request
Example Response
Admin: Create or Update Multiple Departments
Apply one settings object to several departments.
Definition
POST /api/administration/infoboard/department-settings
Request Keys
department_ids*
array
-
IDs of departments that receive the settings.
settings*
object
-
Complete Infoboard settings object applied to every department.
Keys with * are required.
Behavior
New records use the authenticated user as
user_id.Existing records are matched by
department_id; theirsettingsand timestamps are updated while their existinguser_idremains unchanged.The response is the raw list of affected settings records rather than a success wrapper.
Example Request
Example Response
Admin: Delete by Department
Delete InfoboardDepartmentSettings for one department.
Definition
DELETE /api/administration/infoboard/department-settings/{department}
Route Parameters
department
integer
Department ID.
Behavior
The settings record is soft-deleted when it exists.
Deleting settings for an existing department without a settings record is idempotent and still returns success.
Example Request
Example Response
Last updated