System Configuration

Overview

System Configuration options control global behavior of the Colabmacs application.
Defaults are provided as a starting point, but administrators should review and adjust these values to match facility policies, access rules, schedules, and onboarding workflows.

Many options directly interact with other system features such as Business Hours, Access Rules, Events, Projects, and Onboarding.

Configuration Options (Summary)

Option	Default	Related Features
default_event_type	model	Events
default_project_type	null	Projects
default_request_type	null	RequestType
equipment-configuration-request-type	model	RequestType
events.late_grace_period	15 minutes	Events
events.miss_grace_period	30 seconds	Events
events.schedule_end_buffer	2 minutes	Events
events.schedule_start_buffer	5 minutes	Events
github-auth-enabled	false	Authentication
google-auth-enabled	false	Authentication
headerLogo	none	UI / Branding
headerLogoDark	none	UI / Branding
logo	none	UI / Branding
logoDark	none	UI / Branding
maintenance-request-type	model	RequestType
microsoft-auth-enabled	false	Authentication
onboarding.allow_team_creation	true	Teams
onboarding.assign_default_team	null	Teams
onboarding.enable	true	Onboarding
onboarding.projects_require_approval	false	Projects
onboarding.teams_require_approval	false	Teams
primary	none	UI / Branding
PrivacyPolicy	none	Onboarding
private-mode	false	User Visibility
secondary	none	UI / Branding
TermsOfService	none	Onboarding
timezone	UTC	Business Hours, Access Rules

Option Details

timezone

Default: UTC

Sets the application’s local timezone.
This value is foundational for scheduling, bookings, and access enforcement.

Example:

America/Toronto

TermsOfService

Default: none Type: string

Rendered at /terms-of-service and required during registration. Supports Markdown formatting.

PrivacyPolicy

Default: none Type: string

Rendered at /privacy-policy and acknowledged during registration. Supports Markdown formatting.

default_event_type

Default: ReservationType: model

Defines the default event type when creating system events.

Branding

logo

Type: image

The primary system logo used on login and registration pages.

logoDark

Type: image

The primary system logo used in dark mode on login and registration pages.

headerLogo

Type: image

The logo used in the application header

headerLogoDark

Type: image

The logo used in dark mode in the application header

primary

Type: color

Primary UI color.

secondary

Type: color

Secondary UI color.

Authentication

google-auth-enabled

Type: boolean

Enable Google OAuth authentication.

github-auth-enabled

Type: boolean

Enable GitHub OAuth authentication.

microsoft-auth-enabled

Type: boolean

Enable Microsoft OAuth authentication.

Projects & Onboarding

default_project_type

Type: model

Automatically assign a project type to new projects.

onboarding.enable

Type: boolean

Enable or disable the onboarding flow.

onboarding.allow_team_creation

Type: boolean

Allow users to create teams during onboarding.

onboarding.teams_require_approval

Type: boolean

Require admin approval for new teams.

onboarding.projects_require_approval

Type: boolean

Require admin approval for new projects.

onboarding.assign_default_team

Type: boolean

Automatically assign new users to a team.

Privacy

private-mode

Type: boolean Restricts visibility of user information.

Events

The following options all support the interval format

events.late_grace_period

Time before an event is considered late.

events.miss_grace_period

Time before an event is considered missed.

events.schedule_start_buffer

Activation buffer before event start.

events.schedule_end_buffer

Completion buffer after event end.

Requests

default-request-type

Type: model

Default type for new requests.

equipment-configuration-request-type

Type: model

Default request type for equipment configuration requests.

maintenance-request-type

Type: model

Default request type for resource issue reports.

Best Practices

• Configure timezone first
• Use approvals in regulated environments
• Review buffers after observing usage
• Revisit defaults as policies evolve