Skip to content

config.rk ​

Layer 4: defaults for an organisation (company). Organisations and members themselves are data in the database, managed in Console; this file seeds defaults and is what Rangka AI edits through change sets.

Lives in <site>/config.rk · Schema config.json (source) · first line: # yaml-language-server: $schema=https://rangka-os.github.io/rangka-os/schema/0.5/config.json

Properties ​

PropertyTypeMeaning
localestring
default "id-ID"
currencyIDR
default "IDR"
timezonestring
default "Asia/Jakarta"
fiscal_year_startstring
default "01-01", pattern ^[0-1][0-9]-[0-3][0-9]$
taxobject
tax.ppn_ratenumber
default 12, min 0, max 100
tax.dpp_ratiostring
default "11/12"
tax.pkpboolean
default false
tax.ppn_fee_onlybooleanPPN on the service fee only: invoice lines marked as the workers' wages (ppn_exclude) stay out of the PPN base (DPP nilai lain, PMK 83/2012). Default false.
default false
numberingmap of string or objectA series (object) or a per-model naming override (string), e.g. sales_invoice: 'INV-{YYYY}-{#####}'
plannamesnake_case, never renamed once released
pattern ^[a-z][a-z0-9_]{0,62}$
themenamesnake_case, never renamed once released
pattern ^[a-z][a-z0-9_]{0,62}$
layoutnamesnake_case, never renamed once released
pattern ^[a-z][a-z0-9_]{0,62}$
ssoobject
sso.domainslist of string
sso.upstreamnamesnake_case, never renamed once released
pattern ^[a-z][a-z0-9_]{0,62}$
sso.requiredboolean
default false
aiobject
ai.enabledboolean
default true
ai.auto_applynever · low_risklow_risk lets Rangka AI apply layer-6 changes (theme, layout, labels) without approval
default "never"
ai.approverslist of nameRoles that can approve change sets
ai.proposerslist of nameRoles (besides the approvers) that can propose change sets from the web app's Ubah mode
default []
onboardingobject
onboarding.processstringThe process Mulai di sini follows (contract 0053 §2)
pattern ^[a-z][a-z0-9_]*$
appslist of nameInstalled apps, in menu order. Must be allowed by the plan.
modulesmap of stringmodule → version range (^1.0, >=1.2): modules installed on their own, next to apps (contract 0032). The validators add each module's requires; the plan must allow them. Not allowed under orgs.<id>.config.
connectorslist of nameConnectors switched on before any flow uses them (contract 0036). Site-wide: not allowed under orgs.<id>.config.
connector_authlist of nameRoles (besides owner) that may set and remove connector secrets through the API (contract 0017 §3). Site-wide.
orgobjectThe legal entity printed on documents
org.legal_namestring
org.npwpstring
org.pkpboolean
default false
orgsmap of objectPer-org settings by org id; an org's config overrides this file's keys for that org (contract 0010)

Example ​

From rangka-apps/examples/sites/kopi-senja/config.rk (first 60 lines):

yaml
# yaml-language-server: $schema=https://rangka-os.github.io/rangka-os/schema/0.5/config.json
locale: id-ID
currency: IDR
timezone: Asia/Jakarta
tax: {ppn_rate: 12, dpp_ratio: 11/12, pkp: true}
numbering:
  invoice: {pattern: "INV-{YYYY}-{#####}", reset: yearly}
apps: [crm]
plan: tumbuh
theme: kopi_senja
layout: crm_first
sso: {domains: [kopisenja.test], required: false}
ai: {enabled: true, auto_apply: never, approvers: [owner, sales_manager]}

Generated from the schema by website/scripts/gen-reference.mjs. Edit the schema, not this page.

Rangka OS is source-available under the Elastic License 2.0 (ELv2). Free to self-host.